Dnia 25-12-2007, wto o godzinie 21:31 +0100, Petter Reinholdtsen pisze: > [Patryk Sciborek] > > I've added few lines to my /etc/network/if-up.d/mountnfs and it > > works for me. > > The patch make sense to me, except for this line: > > PATH="/sbin:/usr/sbin:/bin:/usr/bin" /etc/init.d/o2cb start > > Why do you need to set the PATH before calling o2cb?
Hello! I had to do this because, when system starts PATH during execution of /etc/network/if-up.d/mountnfs is only set to PATH="/sbin:/bin". But /etc/init.d/o2cb requires seq which resides in /usr/bin/. Without this you will see: /etc/init.d/o2cb: line 526: seq: command not found Starting Oracle cluster ocfs2: Failed o2cb_ctl: Unable to access cluster service Cannot initialize cluster Stopping Oracle cluster ocfs2: Failed o2cb_ctl: Unable to access cluster service Cannot initialize cluster mount.ocfs2: Unable to access cluster service Cannot initialize cluster mount.ocfs2: Unable to access cluster service Cannot initialize cluster done. > Btw, does it make sense to move the code to handle o2cb from > initscripts into a o2cb specific package? Probably. I would be nice also if ocfs2 init scripts don't depend on files from /usr which may be not mounted yet. Best Regards, Patryk Ściborek
smime.p7s
Description: S/MIME cryptographic signature
