Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a SLES 9 configuration that boots from hard disk and also uses LVM SAN space for Oracle partitions. For this to work, I had to ensure that LVM was started before raw and Oracle in the run level 3 boot sequence. The modifications made to support this were:
1. Delete existing S12raw symbolic link
2. Delete existing S13oracle symbolic link
3. Create new S16lvm link: ln -s ../boot.lvm S16lvm
4. Create new S17raw link: ln -s ../raw S17raw
5. Create new S18oracle link: ln -s ../oracle S18oracle
After rebooting, all works as expected.
However, I've been finding that after subsequent maintenance reboots the original S12raw and S13oracle links have been reestablished and the S17raw and S18oracle links have vanished. The S16lvm link remains, but it now runs after Oracle, so the LV partitions Oracle expects to find are not yet instantiated and Oracle fails to load properly.
I have rebooted the system multiple times in a row and the new links remain in place - they are automagically changing later. I've checked all crontab files and there's nothing that reverts to the original links.
Any idea what is reverting these links or how to make them persistent?
As one possible solution, can I perform the same symbolic link changes noted in the original post in the file /etc/init.d/boot.local to ensure that the expected boot sequence links are in place prior to starting the run level scripts?
Will /etc/init.d/rc3.d/ be available for manipulation at that point in the boot process?
Unfortunately, update-rc.d nor sysv-rc-conf are SLES 9 utilities. sysv-rc-conf will work for /etc/rc?.d, not /etc/init.d/rc?.d. I've run yast's Runlevel Editor, but it only allows turning services on/off and assigning run levels - not specifying init's script execution ordering.
Perhaps all I really needed to do was add dependencies for boot.lvm to both raw and oracle scripts?
I was able to determine that insserv was reordering the service script symlinks and altered the order using the service script header parameters. For some reason, adding a required startup dependecy for boot.lvm to the raw script had no effect, but adding a dependency for dhcpd to the raw script forced raw and oracle symlinks to move to after the LVM symlink I had created.