LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 08-05-2004, 04:12 PM   #1
Big Money
LQ Newbie
 
Registered: Apr 2004
Distribution: Suse 9.2
Posts: 10

Rep: Reputation: 0
boot.local failed (suse 9.1)


After file association problems with Mandrake (see my other thread...) I switched to Suse, and I love it...

...except that boot.local fails on boot. It's not the permissions (755, the same as all the other boot.whatever files, all of which work), and it's obviously not the contents, since all that's in there are the #! /bin/sh line, and all the comments that it installed with. I even tried re-installing it. Does anyone have any idea what I'm screwing up here?

Thanks
 
Old 08-05-2004, 04:33 PM   #2
rjlee
Senior Member
 
Registered: Jul 2004
Distribution: Ubuntu 7.04
Posts: 1,990

Rep: Reputation: 67
Check it's being called from /etc/rc.d/boot

NB: SuSE uses /etc/rc.d/ for init scripts, not /etc/init.d or /etc/rc.d/init.d/ like some distros.
 
Old 08-05-2004, 05:22 PM   #3
Big Money
LQ Newbie
 
Registered: Apr 2004
Distribution: Suse 9.2
Posts: 10

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by rjlee
Check it's being called from /etc/rc.d/boot

NB: SuSE uses /etc/rc.d/ for init scripts, not /etc/init.d or /etc/rc.d/init.d/ like some distros.

With my 9.1 install, the rc.d folder is just a symbolic link to init.d. Are you saying I should actually make an rc.d folder and put boot.local in it? And why are the rest of the boot.whatever scripts working if they're in /etc/init.d?
 
Old 08-05-2004, 05:27 PM   #4
rjlee
Senior Member
 
Registered: Jul 2004
Distribution: Ubuntu 7.04
Posts: 1,990

Rep: Reputation: 67
Sorry; you're right. I'd gotten so used to using /etc/rc.d that I forgot to check. My mistake.

No you shouldn't need to create an rc.d folder, but you may need the symbolic link.
 
Old 08-05-2004, 09:45 PM   #5
bruno buys
Senior Member
 
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,509

Rep: Reputation: 46
This script is just a skeleton, for people to add things. If you don't use it for anything, just remove it from boot. You can use yast2 or sysv-init Editor to remove it.
 
Old 08-05-2004, 10:46 PM   #6
Big Money
LQ Newbie
 
Registered: Apr 2004
Distribution: Suse 9.2
Posts: 10

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by bruno buys
This script is just a skeleton, for people to add things. If you don't use it for anything, just remove it from boot. You can use yast2 or sysv-init Editor to remove it.
Uhh... yeah, except I'm looking for help on getting it working, not on removing it. Thanks though.
 
Old 08-06-2004, 04:37 AM   #7
/bin/bash
Senior Member
 
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802

Rep: Reputation: 46
The boot.local is just a blank file with some comments. If you want to add a command to the end of the boot process you put the command in boot.local. It's the equivalent of the rc.local file for other distros. What is the error?, and could you post the contents of the file?
 
Old 08-06-2004, 07:27 AM   #8
bruno buys
Senior Member
 
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,509

Rep: Reputation: 46
Thatīs what I meant. Whatīs the point in running a thing that do nothing?
 
Old 08-06-2004, 10:05 AM   #9
Big Money
LQ Newbie
 
Registered: Apr 2004
Distribution: Suse 9.2
Posts: 10

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by /bin/bash
The boot.local is just a blank file with some comments. If you want to add a command to the end of the boot process you put the command in boot.local. It's the equivalent of the rc.local file for other distros. What is the error?, and could you post the contents of the file?
Yup, did that, too. It was failing with nothing in it (aside from the default comments), so I put a line in there (ntpdate to sync the clock with adjtimex to come when I get it fixed), and it still fails. It doesn't really fail with any errors, it just says "Running boot.local" or whatever it says on the left side during the boot sequence, then comes up with the red "failed" on the right. I checked the boot messages, which say this...

System Boot Control: Running /etc/init.d/boot.local
failed<notice>killproc: kill(456,3)

I was thinking that the killproc statement may have held a clue, but I saw one like it (exactly like it, except the "3" was a "29") a few messages before it, like so...

Creating /var/log/boot.msg
done<notice>killproc: kill(456,29)

So yeah, I'm still clueless here. (And I'm probably going to kick myself if I ever find out what's wrong...)
 
Old 08-06-2004, 02:10 PM   #10
/bin/bash
Senior Member
 
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802

Rep: Reputation: 46
OK it possibly has some escape character or something you can't see with your editor. I would just delete the file and make a new one. All it needs is the shebang line then a comment as to the purpose of the file: Here is mine.

#! /bin/sh
#
# Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights reserved.
#
# Author: Werner Fink <werner@suse.de>, 1996
# Burchard Steinbild, 1996
#
# /etc/init.d/boot.local
#
# script with local commands to be executed from init on system startup
#
# Here you should add things, that should happen directly after booting
# before we're going to the first run level.
#
rm -fr /tmp/*
rm -fr /tmp/\.[a-Z]*

<EDIT> Also check that the symlink /bin/sh is good and points to the correct shell.
ls -l /bin/sh
lrwxrwxrwx 1 root root 4 2004-08-05 17:08 /bin/sh -> bash*

Last edited by /bin/bash; 08-06-2004 at 02:13 PM.
 
Old 08-06-2004, 09:59 PM   #11
Big Money
LQ Newbie
 
Registered: Apr 2004
Distribution: Suse 9.2
Posts: 10

Original Poster
Rep: Reputation: 0
So here's where the whole "kicking myself" starts.

It looks like the script will come up as failed if a line in it doesn't exit cleanly. The reason my ntpdate command wasn't exiting cleanly was because the network is brought up after boot.local executes. So I'm either running ntpd, or I'm looking for more startup scripts... whee...

Thanks to everyone for the ideas.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
failed to send 'clear' to local ypserv: RPC:Program not registered beginner16 Linux - Newbie 3 04-29-2014 12:25 PM
Help! Open SUSE 10.0 boot failed after first CD install Sword7 Suse/Novell 2 10-11-2005 07:08 AM
Failed opening '../main/mainconfig.php' for inclusion (include_path='.:/usr/local/lib ryancoolest Linux - Newbie 3 09-29-2004 09:10 PM
local network configure failed xround Linux - Networking 10 08-25-2004 05:19 AM
Stop Suse boot.local in Grub crazibri Linux - Newbie 25 07-02-2004 08:21 AM


All times are GMT -5. The time now is 10:10 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration