On Wed, Mar 15, 2006 at 02:14:19PM +0100, Robin Elfrink wrote: > On a (just yesterday installed) FreeBSD 5.4 server I get (the binary is > /usr/sbin/amavisd):
I don't think this is relevant, since we use the ps from procps (gnu/linux utils). > On my Debian GNU/kFreeBSD box I get (the binary is /usr/sbin/amavisd-new): > > amavis 69243 0.0 0.0 26812 0 ? S Mar09 0:00 > /usr/bin/perl -T /usr/sbin/amavisd-new start > > On a up-to-date Ubuntu box I get (the binary is /usr/sbin/amavisd-new): > > amavis 12989 0.0 1.8 17864 14732 ? Ss 14:07 0:00 amavisd > (master) Interesting. What happens if you run it manualy? I can't reproduce this difference with other perl programs (on gnu/linux, "/usr/bin/perl" is always part of the exec command). > The amavisd-new binary on Ubuntu seems to tell the system that it's > process name is 'amavisd <something>'. I assume the kFreeBSD package is > mostly the same as Ubuntu's, so amavisd-new on kFreeBSD somehow fails to > tell the kernel it's process name, or the kernel does not listen. > > Is my logic going in the right direction? > > I remember some time ago having done some programming in C and calling a > function to set the process name. But this stuff is in perl so there's > probably a perl function for it, which fails. > > Still going in the right direction? Sounds like it. -- Robert Millan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
