Ok guys, thanks for the feedback. After your good comments, and in order to help people looking for a rc.local, I think we can say that the example script given is correct, and that, once the 4 steps are done, the commands contained at the end of the script will be launched after the system has booted. When I wrote the script, my idea was to do it as compatible as possible with all Suse versions. Probably the "Required-Start: $local_fs $remote_fs $network" entry is not needed (the "X-UnitedLinux-Should- Start: $ALL" entry is sufficient), but I thought that, for old Suse versions that don't support the "X-UnitedLinux-Should-Start" entry (nor the "$ALL" value), it would be sufficient to launch the script after basic services. The optimal thing would be, for those old systems, to include the last launched service as the value, but then a generic rclocal script wouldn't be possible. Please give any suggestion you have to improve the example. Cheers El vie, 22-07-2005 a las 04:57 +0200, Anders Johansson escribió:
On Friday 22 July 2005 04:25, James Knott wrote:
Carlos E. R. wrote:
There is another place you haven't noticed:
/etc/init.d/after.local
That script, if it does exist, is in fact run after "all" scripts, at the end of runlevel change (it is fired from /etc/init.d/rc at the same time it writes "Master Resource Control: ".
;-)
I didn't know about that one. It appears that it should do the trick.
It's new for 9.3 though, so not relevant for all
Both Required-Start: $all and Should-Start: $all will work