busybox "ps ax" woes, was: Re[2]: [Qemu-devel] Config file support

busybox "ps ax" woes, was: Re[2]: [Qemu-devel] Config file support

[Paul Sokolovsky]

Hello Bernhard,

Wednesday, October 25, 2006, 6:35:04 PM, you wrote:

> On Wed, Oct 25, 2006 at 03:18:31AM +0300, Paul Sokolovsky wrote:

>>  Oh, and while we still talking (and to add even more confusion),
>>how'd you guys managed to kill "ps ax" to work in busybox 1.2.1? I
>>really miss it here, when loading my embedded images into QEMU...

> Just unset PS_FEATURE_WIDE.

> In principle, i agree that we should enhance it to allow for
> disregarding any non-options.

  Thanks for your response! I actually had a suspicion that some
busybox config option was mis-set. We're using it here with
OpenEmbedded automated build system, and well, when doing system
integration, the distance from configs of individual packages
to the developers increases ;-).

  But we actually had issues with that besides mere command-line
nuisance: some of our init.d scripts has "ps -e" or something, and as
a workaround we had to switch to procps ;-(.

  Again, thanks for your hint, from the context where it was written,
I couldn't expect to get an answer ;-)

> Something like
> Index: libbb/getopt32.c
> ===================================================================
> --- libbb/getopt32.c    (revision 16432)
> +++ libbb/getopt32.c    (working copy)
> @@ -72,6 +72,9 @@
>          env -i ls -d /
>          Here we want env to process just the '-i', not the '-d'.
>  
> + "_"    If the first character in the applet_opts string is an underscore,
> +               ignore all non-option arguments.
> +
>  const struct option *applet_long_options
>  
>          This struct allows you to define long options.  The syntax for



> Alternatively you can rewrite ps to match the procps' big ps better.
> I need to be able to see the full commandline if i do `ps ww´, not only
> the first 25 chars of them.

> HTH,



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com