Yup. It is very simple, it does not work :) (html-)Highlighted error cmd
below. "no" is the default ps-prog for some reason in my dist of hardy at
least.

Line numbers might not be 100% correct since I've added some debug print
statements but +- 1 or two rows.

Example wich does not work.
ps-watcher --config=/etc/ps-watcher.conf --syslog --nodaemon --sleep=10
--log --debug=10
*PS-CMD: no -e -o pid= -o cmd=*
11/23/09 09:38:39 ps-watcher[32233]: Starting: $Id: ps-watcher.in.in,v 1.57
2006/03/10 19:07:05 rockyb Exp $
Can't exec "no": No such file or directory at /usr/bin/ps-watcher line 576
(#1)
    (W exec) A system(), exec(), or piped open call could not execute the
    named program for the indicated reason.  Typical reasons include: the
    permissions were wrong on the file, the file wasn't found in
    $ENV{PATH}, the executable in question was compiled for another
    architecture, or the #! line in a script points to an interpreter that
    can't be run for similar reasons.  (Or maybe your system doesn't support
    #! at all.)

When I change row 335 from
$opts{ps_prog}      = 'no';   # Where is ps?
to
$opts{ps_prog}      = '/bin/ps';   # Where is ps?

I get this:
ps-watcher --config=/etc/ps-watcher.conf --syslog --nodaemon --sleep=10
--log --debug=10
PS-CMD: /bin/ps -e -o pid= -o cmd=
11/23/09 09:41:55 ps-watcher[32320]: Starting: $Id: ps-watcher.in.in,v 1.57
2006/03/10 19:07:05 rockyb Exp $

= perfect


Cheers

//Marcus


On Mon, Nov 23, 2009 at 9:24 AM, cyco <ubu...@cyconet.org> wrote:

> Could you please document, what is your exact error? What are the
> symptoms of it? Maybe you got a error message?
>
> --
> ps-watcher package bad default ps-prog
> https://bugs.launchpad.net/bugs/486997
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ps-watcher” package in Ubuntu: New
>
> Bug description:
> Binary package hint: ps-watcher
>
> Around line 335 in /usr/bin/ps-watcher you will find this snippet right
> after installing
> ...
> $opts{ps_prog}      = 'no';   # Where is ps?
> ...
>
> which of course will not work.
>
> Changed it to:
> $opts{ps_prog}      = '/bin/ps';   # Where is ps?
>
> which works.
>
> I found it by issuing this so I can see all info in the foreground:
>
> ps-watcher --config=/etc/ps-watcher.conf --syslog --nodaemon --sleep=10
> --log --ps-prog=ps --debug=10
>
> Cheers
>
> //Marcus Herou
>


-- 
Marcus Herou CTO and co-founder Tailsweep AB
+46702561312
marcus.he...@tailsweep.com
http://www.tailsweep.com/

-- 
ps-watcher package bad default ps-prog
https://bugs.launchpad.net/bugs/486997
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to