Re: Process size.
На Thu, 14 Aug 2008 15:33:57 +0800 Eugene Grosbein [EMAIL PROTECTED] записано: On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote: $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Try to eslablish 'vmemoryuse' limit also. It works well, thank you. -- Sincerely, Sergey Chumakov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Process size.
Hello, FreeBSD 7.0-RELEASE-p3 #3 $top ... PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 36032 root 2838 440 1917M 1493M ucond 0 406:39 3.03% CGServer ... $cat /boot/loader.conf.local ... kern.maxdsiz=1073741824 kern.maxssiz=134217728 kern.dfldsiz=1073741824 $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Thank you for answers. -- Sincerely, Sergey Chumakov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Process size.
On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote: $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Try to eslablish 'vmemoryuse' limit also. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Process size.
On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote: Hello, FreeBSD 7.0-RELEASE-p3 #3 $top ... PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 36032 root 2838 440 1917M 1493M ucond 0 406:39 3.03% CGServer ... $cat /boot/loader.conf.local ... kern.maxdsiz=1073741824 kern.maxssiz=134217728 kern.dfldsiz=1073741824 $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Do resource limits apply to root? I wonder if it's an issue of calculation in top; top might be including page sizes and other VM-related things, while limits datasize and stacksize may only be specific to those allocated amounts. If this machine was running RELENG_7 (STABLE), it would have procstat, which could help discern where the extra memory is. Also: is this i386 or amd64? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Process size.
На Thu, 14 Aug 2008 00:44:30 -0700 Jeremy Chadwick [EMAIL PROTECTED] записано: On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote: Hello, FreeBSD 7.0-RELEASE-p3 #3 $top ... PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 36032 root 2838 440 1917M 1493M ucond 0 406:39 3.03% CGServer ... $cat /boot/loader.conf.local ... kern.maxdsiz=1073741824 kern.maxssiz=134217728 kern.dfldsiz=1073741824 $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Do resource limits apply to root? Yes, of course. I wonder if it's an issue of calculation in top; top might be including page sizes and other VM-related things, while limits datasize and stacksize may only be specific to those allocated amounts. If this machine was running RELENG_7 (STABLE), it would have procstat, which could help discern where the extra memory is. Also: is this i386 or amd64? i386 -- Sincerely, Sergey Chumakov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
