SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ok..pulling my hair out!!! Where/how does dhcpc get invoked? The problem I'm having is that whenever my power suddenly goes out, the dhcpc-ethX.pid file doesnt get deleted as with a normal shutdown. When the box comes back up, it sees the old .pid file and doesnt initialize the interface.I've written a script to delete the junk .pid file, but I need to know where in which script to put it.
If the power dropping out is a forever problem, try making a softlink pointing /var/run into the system ramdisk /dev/shm
That way all the pids get dropped when the system dies..
The ifup/ifdown script should be doing a ps ax to match the process name with the pid file to prove it is/isn't stale...
Have a look at /etc/inittab and follow the rc files from there.
It will be called from the sysinit rc file..
What specifically happened was...eth0 was my internal lan and eth1 was my external interface to the net, but, me being me, I wanted to swap them over making eth1 my internal and eth0 the external. I simply edited the rc.inet1.conf script and just swapped the info around. Now, for some unbeknownst reason, if I reboot the box, eth0 never gets a DHCP response and eth1 never initializes. ifconfig only shows loopback and eth0. But if i shutdown the box and power it back up, all is well. What gives?
PS -- I had also deleted all of the old stuff out of the dhcpc folder after i swapped all of the settings over so the box wouldnt get confused.
Hmmm..
I'm not a Slack user so I don't know how it handles runlevels, but it sounds like there is a different rc. closing sequence for shutdown than reboot.
That's normal in distros, esp SysV style, but have a look and see if you can spot the difference..
Originally posted by natedawg_38929 ok..pulling my hair out!!! Where/how does dhcpc get invoked? The problem I'm having is that whenever my power suddenly goes out, the dhcpc-ethX.pid file doesnt get deleted as with a normal shutdown. When the box comes back up, it sees the old .pid file and doesnt initialize the interface.I've written a script to delete the junk .pid file, but I need to know where in which script to put it.
It is invoke by
/etc/rc.d/rc.inet1
When the power come back on, you can cd /etc/rc.d
./rc.inet1 stop
./rc.inet1 start
Or you can delete the dhcpc-ethX.pid file manually in /etc/dhcpc
for some reason unbeknownst to me...after cron had a chance to run overnight, all is well. I say that cron was the answer, but all I know is, that everything was in order the next day. I rebooted the machine several times and everything is fine. Thanx for all of the replies!! If anyone might know why cron had something, if at all, to do with the solution, let me know...later guys!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.