Your problem is that the commands you use to change the value starts a
new shell, changes the value in the new shell, then that shell exits.
The "ulimit" command only affects the current and child shells, not the
parents.
If you want to change the value permanent you can add the following line
to /etc/profile or ~/.profile:
---
ulimit -c
---
Example:
---
root@ROOter-Uppsala:~# ulimit -c
0
root@ROOter-Uppsala:~# busybox sh -c 'ulimit -c 1024'
!! This starts a new shell, changes the ulimit value in that shell, then
it exits and you are back with your first shell
root@ROOter-Uppsala:~# ulimit -c
0
!! no change
root@ROOter-Uppsala:~# ulimit -c 1024
!! "ulimit" is a shell built in command, so this changes the value in
!! the current shell
root@ROOter-Uppsala:~# ulimit -c
1024
---
Den 2016-12-09 kl. 01:50, skrev lukgeeker(lulu):
dear busybox:
busybox version is v1.23.2
The following command is not valid :
1,busybox sh -c 'ulimit -c 1024 true'
2,busybox sh -c 'ulimit -c 1024'
After view or:
[root@lukgeeker]# busybox ash -c 'ulimit -a'
-f: file size (blocks) unlimited
-t: cpu time (seconds) unlimited
-d: data seg size (kb) unlimited
-s: stack size (kb) 8192
-c: core file size (blocks) 0
-m: resident set size (kb) unlimited
-l: locked memory (kb) 64
-p: processes 693
-n: file descriptors 1024
-v: address space (kb) unlimited
-w: locks unlimited
-e: scheduling priority 0
-r: real-time priority 0
why?
thk!!!
!DSPAM:584a0005186451715223260!
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
!DSPAM:584a0005186451715223260!
--
Real life: Thomas Törnblom Email: [email protected]
Snail mail: Banvallsvägen 14 Phone: +46 18 32 31 18
S - 754 40 Uppsala, Sweden Mobile: +46 76 209 8320
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
