On Sat, 9 Jan 1999, Vincent van't Hoog wrote:
After I installed linuxconf1.13r9 I got lots of trouble. Even after I disabled SuSEconfig in the config.rc file. It looks like linuxconf was not aware of the suse init scripts at bootup, because things like the apache server got started twice, and even worse, my
If it got started twice it's due to multiple symlinks for the same program in /sbin/init.d you can probably just delete the extra one so it doesn't try to run it twice. The start and stop scripts are in the /sbin/init.d/rc* subdirectories and all use an S or K , one for starting and the other for stopping a daemon. If it's at rl 2, cd /sbin/init.d/ rc2.d, and grep Apache. There _should_ be two copies, but you'll prob see _4_. Find the one linuxconf added ( look at mod dates ) and just remove it. You can also use rctab to edit the run levels and make corrections ( man rctab.)
whole ISDN configuration is wrecked. Is there a way to delete linuxconf and getting the suse init scripts back at work? I already tried to delete linuxconf with rpm, but the booting process is still not wat it was Vincent
Using linuxconf on S.u.S.E. is like using a snow blower in May on a Florida swamp. If you want to get your boot system back to normal you have to have some ideas about what the setup was before you made changes. Most likely you had a vanilla setup. You might want to mount the livefilesystem cd ( CD #5 ) and look at /sbin/init.d there to get some ideas of what the vanilla setup looks like and just emulate that. Understand the structure there and how it works: it's just a bunch of scripts executed at run levels. The files are commented. There are also a bunch of scripts assocated with runlevels that are executed when entering that runlevel. If you're really lazy ( and I've never tried this ) back up your screwed up /sbin/init.d dir ( mv /sbin/init.d /sbin/init.d-bak) and then cp the /sbin/init.d from the bootdisk and see if that works ( cp -adr /mnt/cdrom/sbin/init.d /sbin/init.d ). Note this is just an idea off the top of my head and I haven't tried it. I think with a little investigation it shouldn't be too hard to get things back to normal, especially if you haven't made a lot of mods from the basic installation. If you have any doubts read the files in /sbin/init.d and check out the information on the S.u.S.E. boot process ( initialization and run levels ) in the S.u.S.E. manual. Good Luck, -M - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>