On Tue, Aug 02, 2005, Doug Summers wrote: > Matthias Kurz wrote: > >On Mon, Aug 01, 2005, Doug Summers wrote: > > > > > >>This has happened twice to me today - once on Solaris 9 and the other on > >>HPUX 11.00/64. The proper init.d scripts are in place on both systems > >>(/sbin/init.d and /etc/init.d) and the K & S scripts are located here: > > > > > >Does this happen "sometimes" or always ? > >Does it run when you call ".../init.d/openpkg start" ? > >Did you look into .../init.d/openpkg ? It checks, whether it can access > >the "rc" of the "openpkg" instance. Is there any possibility that the > >"rc" is not available. All disks should be mounted, when S99openpkg runs, > >though. > >Did you change the value of $openpkg_rc_def ? > > > >You can try to run "/openpkg/etc/rc -v all start" or edit > >.../init.d/openpkg > >and include the "-v" option. Maybe you can see the problem.
> The only time it's failing is on a reboot and only with HPUX & Solaris. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ So, this means it works, when you're calling "openpkg rc all start" manually ? > My RHEL machines works fine; the only difference I can see is that the S > & K scripts on Linux are symlinks to /etc/init.d and the others are the > actual scripts. Well, the K/S scripts should be hardlinked to the script in /etc/init.d (at least under Solaris). Is this the case ? (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) << ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org