Quick one, I'm finding on this one box (8.1) that when machine is rebooted the IP address changes back to a 192.*
when I run /etc/rc.d/rc.inet1 it again sets it us as intended.

Any ideas where to look to see why this is happening?

rc.inet1 is executable and does indeed set IP as intended when run.

Thanks in advance...

What is the IP address supposed to be? What do you have in your rc.inet1.conf pertaining to that device?

I'm not near the machine but the rc.inet1 config is correct as in when run it sets the IP, NetMask and GW as I expect, but this should happen at boot time, as it does on all my other slackware variants but for some reason on this machine when rebooting, this is not happening and IP remains 192.whatver. Yet, I can login and run rc.inet1 and all is as expected.

What is your normal IP address for the computer? Do you notice any output from dhcpcd when you boot the machine? Has the machine always done this or did it just start happening recently?

Its a process machine, was never networked until recently (didnt need to be). The default IP would have been 192.168.1.1 (I think). The correct entries have been added to the rc.inet1 file (no rc.inet1.conf file on 8.1 I recal)

It is executable, when I run it, IP changes and all works as intended until reboot.

dhcpd not running

can't always be near mahicne when rebooted, part of my issue and dmesg doesnt show much or far enough back to boot.

Does the I ever change? Else why not set it statically (not sure if that's what you did already), and after that even make the relevant files non writable?

It's set as a static IP in rc.inet1

I'm not so sure would be best idea to make rc.inet1 non writable, but guess I could backup and do so.

I'll test rebooting on Mon and see if I can see where it is defaulting back to 192.168. I'm assuming it must be happening after rc.inet1 is run as when I run that manually, it does as expected and sets IP etc.

Maybe you could run a grep in the rc.d directory for 192.168 and see if something else sets it later (like rc.local). Can you also post your rc.inet1 file?

Sorry if I'm not correct on files/folders. I didn't start using Slack until the 10 series, so I have no experience with Slack 8 (and even if I did, it would've been long enough ago I doubt I'd remember it very well).

The box has never been able to mount a usb stick, so getting any files from there isnt so easy, but thats another story. It is networked but not to the outside world so to speak.

That said, I checked all of the rc.d dir and found nothing that looked as though it was changing the IP, nothing in rc.local (related anyway).

My dirty work around was to cron rc.inet1 but that gives me shivers LOL

I had hoped there would be a log somewhere that showed IP changes etc, but never really had the need for such before and been running slack for too many years.

There isn't one, but that doesn't prevent you from making your own. Instead of thinking of the init system as a black box, just think of it as some dodgy shell scripts that need debugging, because that's exactly what it is. Edit rc.M and/or rc.inet1 to write stuff to /tmp. Read, digest, refine, repeat, understand, solve. And then give thanks unto "Bob" that Slackware-8.1 did not feature systemd.

Here's a start to get you thinking. I won't tell you exactly what edits to make because strangely enough I find myself without access to a Slackware-8.1 system this morning.

1 members found this post helpful.

Solved, was hidden in an application startup script called from rc.local (doh)

Thanks for all help folks...