pidof: invalid option -- x

[Denys Vlasenko]

On Wednesday 26 December 2007 18:34, Tallam, Sreenivas wrote:
> Hi All,
>
> I am trying to bring up the root file system on a PPC 405 chip using a
> flavor of Montavista Linux (4.0.1) wich has linux version 2.6.10 .
> As the root file system system comes up, some of the daemons throw the
> following error.
>
> Starting system log daemon: syslogd klogdpidof: invalid option -- x
> BusyBox v1.01 (2006.06.06-15:58+0000) multi-call binary
>
> No help available.
>
> .
> Starting periodic command scheduler: cron/var/spool/cron: No such file
> or directory
> /var/spool/cron: created
> crontabs: No such file or directory
> crontabs: created
> pidof: invalid option -- x
> BusyBox v1.01 (2006.06.06-15:58+0000) multi-call binary
>
> No help available.
>
> .
> Starting OpenBSD Secure Shell server: sshdMissing privilege separation
> directory: /var/empty/sshd
> pidof: invalid option -- x
> BusyBox v1.01 (2006.06.06-15:58+0000) multi-call binary
>
> No help available.
>
>  failed (255: ).
>
>
> But once I get to the linux prompt, I see
>
> # ps
>   PID  Uid     VmSize Stat Command
>     1 root        576 S   init
>     2 root            SW< [ksoftirqd/0]
>     3 root            SW< [desched/0]
>     4 root            SW< [events/0]
>     5 root            SW< [khelper]
>    10 root            SW< [kthread]
>    24 root            SW< [kblockd/0]
>    60 root            SW  [pdflush]
>    61 root            SW  [pdflush]
>    63 root            SW< [aio/0]
>    62 root            SW  [kswapd0]
>   627 root            SW  [mtdblockd]
>   581 root            SW  [kseriod]
>   704 root            SWN [jffs2_gcd_mtd6]
>   706 root            SWN [jffs2_gcd_mtd2]
>   708 root            SWN [jffs2_gcd_mtd7]
>   717 root        704 S   syslogd -m 0
>   831 root        460 S   /sbin/klogd -x
>   952 bin         476 S   /sbin/portmap
>   974 root        468 S   /usr/local/bin/pktd_reader
>   998 root        460 S   /usr/local/bin/watcher
>   999 root        780 S   -sh
>  1862 root        688 R   ps
>
> Can someone help me as to why I am seeing the pidof error?

Because busybox pidof does not support option -x.

The error is reported in such an idiotic form because
startup script writer apparently did this:

echo -n "Starting system log daemon:"
echo -n " syslogd"
<starts syslogd>
echo -n " klogd"
<starts klogd>
echo

and it didn't occur to him/her that any error messages
printed in between will totally mess up output.
--
vda