Did you not see my answer from last Friday? You are not using the command correctly. --- 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 1024 --- 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 --- > 16 dec. 2016 kl. 04:50 skrev lukgeeker(lulu) <[email protected]>: > > 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' > > Result: > > > [root@lukgeeker]# busybox ash -c 'ulimit -a' > > -c: core file size (blocks) 0 > > why? > thk!!! > !DSPAM:585364ab840485765980! > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox > > !DSPAM:585364ab840485765980! _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
