script problem

[H.Merijn Brand (procura]

Might it be that the script uses something from a disk that is not *YET* mounted at boot time?

[James R. Ferguson]

Hi:

OK, so are you relying on something else that has *not* yet started when your script is launched??? That is, you have linked it into the startup sequence too early???

Regards!

...JRF...

[John Strang]

Hi Domenico,
Don't be offended by this, but have you checked permissions in /sbin/rc3.d and in /sbin/init.d

And is the script in /sbin/rc3.d correctly named and linked to the script in /sbin/init.d

John

[Mark Greene_1]

>>All work correctly, with -x, with path, with all

but at boot time no!! Sigh Sigh <<

When you rebooted the system, what did the error log show? If it was empty, or if the timestamp on the file did not change from when you ran it at the command line (if you did that first), then that suggests that your script is not getting started at all during boot, and that there is a setup piece missing.

mark

[S.K. Chan]

When you link it in rc3.d, make sure that's the last startup script. Choose a higher SXXX
number.

[harry d brown jr]

Does the script require any volumes to be mounted, the network to be up and running, a database to be started? It could be just a matter of boot sequence.

Can you post the script?

live free or die
harry

[Domenico_5]

hi guys

yes, it's the last in rc3.d

On a Workstation whit the same OS all work correctly

[James R. Ferguson]

Hi (again):

You certainly have a lot of curiosity generated. Several folks have asked you to *please post the script*. Well?

Regards!

...JRF...

[Mladen Despic]

Domenico,

/sbin/rc3.d/S101nrpe star_msg

and

/sbin/rc3.d/S101nrpe start

are valid tests. You can try rebooting into a single-user mode. Do 'mount -a' and then run the same tests.

The other two commands:

/sbin/rc3.d/S101nrpe stop_msg

and

/sbin/rc3.d/S101nrpe stop

should be replaced by:

/sbin/rc2.d/K899nrpe stop_msg

and

/sbin/rc2.d/K899nrpe stop

respectively.

Mladen

[Carlos Fernandez Riera]

While you try... put it in /sbin/rc4.d/S100xxx


And then you will do: init 4


insert :

exec 2>/tmp/whatishappening
set -x


on the first lines of your scripts...
if /tmp/whatishappening exists at least you know the script have been executed, and the errors produced...