ldo@theon:~> diff -u <(ulimit -Sa) <(ulimit -Ha)
--- /dev/fd/63 2025-06-20 16:23:40.206493901 +1200
+++ /dev/fd/62 2025-06-20 16:23:40.206493901 +1200
@@ -1,16 +1,16 @@
real-time non-blocking time (microseconds, -R) unlimited
-core file size (blocks, -c) 0
+core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 124021
max locked memory (kbytes, -l) 8192
max memory size (kbytes, -m) unlimited
-open files (-n) 1024
+open files (-n) 524288
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
-stack size (kbytes, -s) 8192
+stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 124021
virtual memory (kbytes, -v) unlimited

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 6/20/25 12:26 AM, Lawrence D'Oliveiro wrote:

ldo@theon:~> diff -u <(ulimit -Sa) <(ulimit -Ha)
--- /dev/fd/63 2025-06-20 16:23:40.206493901 +1200
+++ /dev/fd/62 2025-06-20 16:23:40.206493901 +1200
@@ -1,16 +1,16 @@
real-time non-blocking time (microseconds, -R) unlimited
-core file size (blocks, -c) 0
+core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 124021
max locked memory (kbytes, -l) 8192
max memory size (kbytes, -m) unlimited
-open files (-n) 1024
+open files (-n) 524288
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
-stack size (kbytes, -s) 8192
+stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 124021
virtual memory (kbytes, -v) unlimited

Uh ... ?QUE?

Beware of what 'top' tells you. Seeing 100+ percent
CPU use is common - but the load is actually split
over more than one cores.

Determining REAL load can sometimes be a bit tricky
in Linux.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 20 Jun 2025 01:19:49 -0400, c186282 wrote:

Beware of what 'top' tells you. Seeing 100+ percent CPU use is common
- but the load is actually split over more than one cores.

Determining REAL load can sometimes be a bit tricky in Linux.

'I' will toggle between the Irix and Solaris modes.

"Also for multi-processor environments, if Irix mode is Off, top will
operate in Solaris mode where a task's cpu usage will be divided by the
total number of CPUs. You toggle Irix/Solaris modes with the `I'
interactive command."

"System Monitor' on Ubuntu has a toggle and defaults to dividing; top
defaults to Irix. He may not have had 'Show All Processes' set in System Monitor but a person in r/Ubunutu couldn't figure out what was bogging
down the machine. top showed it was a service for video/gaming.

'1' in top will show usage by core, although it's not the most intuitive presentation. htop has a better presentation as far as cores but isn't as straight forward for processes.

I hate to say it but Windows tools are a bit more polished.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)