[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: disable problem+question
From: |
mandrews |
Subject: |
RE: disable problem+question |
Date: |
Sun, 23 Mar 2003 21:19:09 -0500 |
Dang, right you are. So much for my new innovation. I could have sworn I had
used non-shell scripts as init/rc script in solaris but apparently not. I
suppose the answer is to use the repository=some_other_dir option to disable -
but this is even less tested than my last answer.
Martin
----
Martin Andrews
martin.andrews@lionbioscience.com
> -----Original Message-----
> From: help-cfengine-bounces+mandrews=cle.lionbioscience.com@gnu.org
> [mailto:help-cfengine-bounces+mandrews=cle.lionbioscience.com@
> gnu.org]On
> Behalf Of Darren Dunham
> Sent: Sunday, March 23, 2003 5:06 PM
> To: Help-cfengine@gnu.org
> Subject: Re: disable problem+question
>
>
> >
> > Since disable actions move the file to *.cfsaved it does
> not work well for init/rc scripts (where the renamed file is
> still processed). Instead I have been removing the execute
> permssions like so:
> >
> > files:
> > /etc/rc2.d/S85power mode=a-x action=fixplain
>
> I'm surprised that does anything at all. On Solaris, the startup
> scripts aren't "run", they're passed as explicit arguments to /bin/sh,
> so execute permission isn't required, only read permission.
>
> /bin/sh /etc/rc2.d/S85power start