← Home ← Back to /g/

Thread 106267098

16 posts 10 images /g/
Anonymous No.106267098 >>106267129 >>106267290 >>106267336 >>106267539 >>106267721 >>106267727
QUICK NO TIME TO EXPLAIN
RUN THIS COMMAND IN YOUR SHELL:
ulimit

Don't worry you don't even need superuser access or anything. Post your results here.
Anonymous No.106267129 >>106267166
>>106267098 (OP)
ARE YOU TRYING TO HACK ME OP?!
Anonymous No.106267166
>>106267129
No really. Even if you're on Windoze you should spin up your Windows Subsystem For Linux and type it in. Heck it might even be in Powershell. I don't know, I quit using Windows after trying the leaked Longhorn preview back in the day.
Russian Voices in Your Head No.106267290
>>106267098 (OP)

% ulimit
unlimited
Anonymous No.106267336 >>106267540
>>106267098 (OP)
I'll never touch this again, btw. ;3
Anonymous No.106267539
>>106267098 (OP)
oh thank you so much anon, you saved my bacon. Ran it just in time.
Anonymous No.106267540 >>106267594
>>106267336
I like your style.
Anonymous No.106267591
ulimit -a
time(cpu-seconds) unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 8388608
stack(kbytes) 8192
lockedmem(kbytes) 87381
memory(kbytes) 16100776
nofiles(descriptors) 1024
processes 1024
Anonymous No.106267594 >>106267604
>>106267540
Right back at you. If I had 12 more fingers I would have enjoyed emacs more. Curious your top Emacs shell did not support the command but below did.
Anonymous No.106267604
>>106267594
eshell is written in elisp, as a portable scripting language that's "posix-alike" to the best of its ability

it even runs on ms-dos and the amiga

shell is just your system's shell set by your environment, in my case ksh, which I guess supports ulimit being more fully FULLY POSIX
Anonymous No.106267614 >>106267697
computer ksh$ which ulimit
which: ulimit: Command not found.
computer ksh$ ulimit
unlimited

Must be some trick with this eh?
Anonymous No.106267697
>>106267614
It is built into the shell, if supported.
https://github.com/bminor/bash/blob/master/builtins/ulimit.def
Anonymous No.106267721 >>106267726
>>106267098 (OP)
>man ulimit
>No manual entry for ulimit
>which ulimit
>No ulimit in PATH
>...
>fuck it, try it anyway
>ulimit
>unlimited
Fuck, did I got pwned?
Anonymous No.106267726
>>106267721
You are part of the botnet, now.
Anonymous No.106267727 >>106267731
>>106267098 (OP)

ulimit [-HSTabcdefilmnpqrstuvx [limit]]
Provides control over the resources available to the shell and to processes started by it, on systems that allow such control. The -H and -S options specify that the hard or soft limit is set for the given resource. A hard limit cannot be increased by a non-root user once it is set; a soft limit may be increased up to the value of the hard limit. If neither -H nor -S is specified, both the soft and hard limits are set. The value of limit can be a number in the unit specified for the resource or one of the special values hard, soft, or unlimited, which stand for the current hard limit, the current soft limit, and no limit, respectively. If limit is omitted, the current value of the soft limit of the resource is printed, unless the -H option is given. When more than one resource is specified, the limit name and unit are printed before the value. Other options are interpreted as follows:
-a

All current limits are reported

-b

The maximum socket buffer size

-c

The maximum size of core files created

-d

The maximum size of a process's data segment

-e

The maximum scheduling priority ("nice")

-f

The maximum size of files written by the shell and its children

-i

The maximum number of pending signals

-l

The maximum size that may be locked into memory

-m

The maximum resident set size (many systems do not honor this limit)

-n

The maximum number of open file descriptors (most systems do not allow this value to be set)

-p

The pipe size in 512-byte blocks (this may not be set)

-q

The maximum number of bytes in POSIX message queues

-r

The maximum real-time scheduling priority
Anonymous No.106267731
>>106267727

-s

The maximum stack size

-t

The maximum amount of cpu time in seconds

-u

The maximum number of processes available to a single user

-v

The maximum amount of virtual memory available to the shell

-x

The maximum number of file locks

-T

The maximum number of threads
If limit is given, it is the new value of the specified resource (the -a option is display only). If no option is given, then -f is assumed. Values are in 1024-byte increments, except for -t, which is in seconds, -p, which is in units of 512-byte blocks, and -T, -b, -n, and -u, which are unscaled values. The return status is 0 unless an invalid option or argument is supplied, or an error occurs while setting a new limit.