-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Thomas Schulz writes: > > The main prob is that /etc/rc3.d/S91bbmass , and /etc/rc3.d/S91buildbot > > didn't seem to run -- or at least if they *were* run, the daemons didn't > > stay up, and didn't log anything. > > > > There's a possibility that there were $PATH issues, but in case that > > wasn't it: Solaris wizards (assuming there are any here): is there > > anything that needs doing to get a startup script run, apart from putting > > in /etc/rc3.d? I keep hearing stuff about some massively overspecified > > "svc" framework, I hope that's not it. ;) > > The svc stuff is for Solaris 10 or later. Even there you can put scripts > in /etc/rc*.d, but there are some restrictions. Do these scripts run if > you run them manually after the system is up? Is the execute bit set? Yep, both work fine that way. Good to know I don't *have* to mess with svc. > You may have to put some debugging echo lines in the scripts and then > watch the console during boot. I don't think that output to standard out > is logged anywhere, it just appears on the console during boot. Wish I knew where the console went ;) I think the problem was with $PATH -- I guess we'll see what happens next time it reboots. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDuwvZMJF5cimLx9ARAr15AJ9+HHaD9hhMHupEg6tXsqLipbd2+wCfWKxZ EMhlHAXHBov9C5HaSbaiqyA= =vuZb -----END PGP SIGNATURE-----
