Date: Wed, 21 Jan 2009 13:21:15 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-hackers@freebsd.org Subject: Re: ps acting weird? Message-ID: <E1LPb91-000OC2-Qt@kabab.cs.huji.ac.il> In-Reply-To: <alpine.BSF.2.00.0901211105180.13974@fledge.watson.org> References: <E1LPGw2-0008Ja-OX@kabab.cs.huji.ac.il> <alpine.BSF.2.00.0901201544450.74507@fledge.watson.org> <E1LPZXb-000N4U-V6@kabab.cs.huji.ac.il> <alpine.BSF.2.00.0901211105180.13974@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, 21 Jan 2009, Danny Braniss wrote: > > > thanks Robert, it is always educational to read your answers! > > > > i have set kern.ps_arg_cache_limit, as you suggested to 4k, but i think 512 > > would have been enough (excluding those pathological cases of 'command *') > > btw, this tomcat/java command line was 312 (why not use a config file!). > > > > which brings on another issue: > > > > ps -o command= -p 777 > > /usr/local/diablo-jdk1.6.0/bin/java -Djava.endorsed.dirs= -classpath [...] > > while > > ps -o comm= -p 777 > > java > > ps distinguishes "comm", which is the binary name as stored in the process > structure's p_comm field, and the command line, which is p_args. From the > ps(1) man page: > > KEYWORDS > The following is a complete list of the available keywords and their > meanings. Several of them have aliases (keywords which are synonyms). > ... > comm command > command command and arguments hehe, i read the manual :-), hence my question, the only difference, from the manual, is that command is comm and arguments, which now you explained that it's not so. danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LPb91-000OC2-Qt>