[SOLVED] Slackware(64) 15.0 - /etc/rc.d/rc.local is not working

inukaze · 01-30-2024, 03:51 PM

Quote:

Originally Posted by michaelk

What type of ISP? Do you use a VPN service? When you run the script manually the network is up and the script works fine?

Basically if ntpdate is installed it will located in /usr/sbin so whereis is not necessary.

ISP, National for Public Administration.
No we not use VPN service.
yes when i ran the script manually works fine

metaed · 01-30-2024, 04:10 PM

Do you have anything in /etc/rc.d/rc.inet1.conf?

Windu · 01-30-2024, 04:20 PM

Quote:

Originally Posted by inukaze

in the script the right path is solve by this command

Code:

ntpdate=$(whereis -B "/usr/sbin" "/usr/local/sbin" "/sbin" "/usr/bin" "/usr/local/bin" "/bin" -b ntpdate | grep -i "ntpdate" | cut -d " " -f02 | cut -c11-20)

Did you actually verify that? To me it looks like you copy/pasted a lot of code from the internet without understanding what it is supposed to do.

Try running that command

Code:

whereis -B "/usr/sbin" "/usr/local/sbin" "/sbin" "/usr/bin" "/usr/local/bin" "/bin" -b ntpdate | grep -i "ntpdate" | cut -d " " -f02 | cut -c11-20

- it just returns the string "ntpdate", there's no full path.
Use

Code:

which ntpdate

instead, much cleaner.

michaelk · 01-30-2024, 04:58 PM

Quote:

In "ping" during boot the network access is not ready at that point

Do you know the reason why not? Is this a mobile data plan of some type?

rkelsen · 01-30-2024, 05:14 PM

Dissecting what you're trying to do. Please correct me if I'm misunderstanding your goals here.

The first part of the script tests for internet access before syncing with NTP. Why don't you just use NTP as it was designed? It is trivial to set this up in Slackware. There are two steps:
1. Edit /etc/ntp.conf to remove the hashes (# comment marks) from the beginning of lines 19-22.
2. chmod +x /etc/rc.d/rc.ntpd

This will start the NTP daemon which will sit in the background and wait for a network connection before trying to synchronise your clock. I don't understand why you seem to think you need to complicate it so much?

The second part of the script tests if a remote machine is up and then mounts the CIFS shares from that remote machine. Again, this looks far more complicated than it needs to be. I'd second the notion that you may want to set up AutoFS for this instead.

The third part of the script starts QEMU, and is the only part of your script I'd leave in there:

Quote:

Originally Posted by inukaze

Code:

if [ -x /etc/rc.d/rc.qemu-ga ]; then
  # Start QEMU Guest Agent:
  echo "Starting QEMU Guest Agent:    /etc/rc.d/rc.qemu-ga start"
  /etc/rc.d/rc.qemu-ga start
fi

Quote:

Originally Posted by inukaze

With NetworkManager, i need configure the Cisco Switch to use the MAC to get a static ip exclusive for my pc, because the internal DHCP server every time i restart, change the ip.

NetworkManager is somewhat less than ideal for a machine you intend to use as a server. It shines on laptops, netbooks and other devices which are commonly and constantly changing (usually wifi) networks. The problem with NetworkManager, as pointed out above, is that you have to wait for a user to log in to connect to a network... which is pretty useless for a machine you're wanting to use as a server.

To me, it seems like this a machine which should be configured to use a static IP. You can do this using the netconfig script, choosing static IP and following the bouncing ball.

henca · 01-31-2024, 12:51 AM

Quote:

Originally Posted by inukaze

With NetworkManager, i need configure the Cisco Switch to use the MAC to get a static ip exclusive for my pc, because the internal DHCP server every time i restart, change the ip.

I make a internal NTP server with ip 10.48.1.38

Why not simply configure a static IP address in the 10.*-series in your internal network for your computer? Or, if you want to use dhcp, couldn't you use rc.inet1.conf to configure your eth0 to get its address from dhcp? You might need to configure your internal dhcp server to reserve some addresses for static ip addresses unless you want dhcp for all your machines.

I haven't used NetworkManager myself, but isn't it possible to configure NetworkManager to initialize your network at boot instead of waiting for a logged in user to configure the network?

regards Henrik

Slax-Dude · 01-31-2024, 06:36 AM

Quote:

Originally Posted by inukaze

In "ping" during boot the network access is not ready at that point

What I do, in similar situations, is wait for ping to succeed within 10 seconds and if it does, execute code

Code:

timeout 10 bash -c "until ping -c1 192.168.1.100 &>/dev/null; do :; done" && echo "OK" || echo "NOK"

Replace the echo "OK" for your code and the echo "NOK" for an appropriate error message.

Don't worry about adjusting the timeout 10 to something larger like 30 seconds or several minutes, as the script proceeds as soon as ping gets through, not at the end of the timeout.
Initially I had a sleep command but this is better (for me)

inukaze · 02-02-2024, 12:59 PM

I had the follow configuration made it via netconfig

Hostname : Slack64
Domain Name : FUNDAPROAL
IPv4 Addresses : 10.48.8.212 -> Static IP
IPv4 Gateway : 10.48.8.1
Nameserver : 10.48.1.30

Ok, now is solved, just configuring it to use static ip, and during boot the internet access works. using NetworkManager the system wait until the Graphical Session and user session start to activate the internet access, and that was all issue.