Three questions

Here are 3 questions:

  1. how to save a link which always goes to the last post

  2. where is the number of a post shown

  3. seems that only pictures but no text can be uploaded




textfile.txt (47 Bytes)

but needs to have xyz.txt format naming


To the last post on every thread you open? you can save a link to a thread or a specific post only.
To go to last post of a thread simply press the end button

or click on the time for last post:


also, by default, when clicking on the link to a thread you will not be shown the first post in that thread, but the first unread (by you) post in that thread.


…works like a charm when a bit of thinking to kick start intuitiveness is applied. :innocent: Thanks again!

How about:

It’s self explanatory.

I think he is responding to @joekamprad’s screenshot showing him uploading a .txt and that they are supported.

yea my rights differ from yours :wink:

Never mind! It might be helpful, tough. :wink:

question is what for you need to upload text files? there is pastebin and also Hide Details option:


t is normal and can be a good thing for Linux systems to use some swap, even if there is still available RAM. The Linux Kernel will move memory pages that are hardly ever used into swap space to ensure that even more cachable space is made available in-memory for more frequently used memory pages (a page is a piece of memory). Swap usage becomes a performance problem when the Kernel is pressured to continuously move memory pages in and out of memory and swap space.

Another advantage is that swap gives admins time to react to low memory issues. We will often notice the server acting slowly and, upon login, will notice heavy swapping. Without swap (as described in the next section), running out of memory can create much more sudden and severe chain reactions. So usually, I would advise setting swap space to about the size of your largest process. For example, MySQL’s configured memory in my.cnf. It can even be smaller, especially if you have monitoring and/or alerting in place.

Some recommend no swap or swap size slightly larger than the total RAM. If you can come up with valid reasons for this, then that maybe your choice. However, this is hardly the case on servers, and you should instead balance your decision with the effects swap will have on your specific applications. Swap does not change the amount of RAM required for a healthy server, or desktop for that matter. It’s designed to be complementary to the performance of healthy systems.

To summarize:
— Even if there is still available RAM, the Linux Kernel will move memory pages that are hardly ever used into swap space.
— It’s better to swap out memory pages that have been inactive for a while, keeping often-used data in cache, and this should happen when the server is most idle, which is the aim of the Kernel.
— Avoid setting your swap space too large if it will result in prolonging performance issues, outages, or your response time (without proper monitoring/alerts).

Swap Space vs. No Swap when available memory is low

Unlike the case above, if you don’t have enough memory, swap will be used quite often and noticeably more during any memory requirement spikes. If you don’t have enough memory and no swap space, this will often cause failure to allocate memory for requests needing more memory pages. As a last resort, the Kernel will deploy OOM killer to nuke high-memory processes (usually MySQL, java, etc.).

For a more detailed look at Linux swap space, read the Swap Management and Page Frame Reclamation chapters from docs. Also, look at the last section, “Kernel cache pressure and swappiness,” of my other blog post for tips on tuning Linux swap space usage by the Kernel. If your swap space “used” is always ‘0’ then you do indeed have a ton of freely available RAM, in which case it may be safe to remove the swap space… or you can adjust your Kernel’s cache pressure to make use of even more RAM.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.