[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with shellcommand and background job

From: Manon Goo
Subject: Re: Problem with shellcommand and background job
Date: Thu, 17 Feb 2005 23:58:14 +0100

In processes: the problem does not exist. This Only seams to be a bug
in shellcommand:


--On 17. Februar 2005 16:24:10 -0500 Christian Pearce <address@hidden> wrote:

Here is the exact code from our SysNav 5.0 release.  This is what I use
to restart the clients and the server if need be.  Notice I renamed my to for our proxynodes.


            restart "$(bb_prefix)/bb/ start"

            restart "$(bb_prefix)/bbc/ start"

Here is an example of something that held onto the STDOUT, and STDERR.

    # Reboot if scheduled automation occurs
        '$(shutdown) -y -g 300 -i 6 "SysNav is rebooting the server to
install patch Clusters." > /dev/null 2>&1 &'

Notice I pipe both STDOUT and STDERR to /dev/null and then background
it.  This works like a champ.

There is also this like in the wiki.

On Thu, 2005-02-17 at 15:30, David Douthitt wrote:
Manon Goo wrote:
> I  have tried to restart BigBrother from cfengine (2.1.13 )  the
> BigBrother restart script starts some other processes in background
> but these to not close the STDIN and STDERR. Now cfengine habs
> infinite unless I redirect the output of The restart script.

I don't know if there is a way around it, but I believe that is expected
behavior, though incorrect behavior.  The programs should close STDIN
and STDERR, but if they do not then things hang.

I ran into this trying to get some programs to run during system startup
in initialization scripts.

The real question is: can cfengine work around this?  I believe you can
use a shell script to "hold" the process which doesn't close STDIN and
STDERR properly.
Christian Pearce

Help-cfengine mailing list

Attachment: pgp9vlGHCMhLY.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]