-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rc.local depreciated #821
Comments
I see that it's being run on 3.23.4.0 - are you not seeing this? |
Nope. Have to manually run it after the node boots in order to actually set eth0. True on both 3.32.4.0 and the nightly builds |
Could you add the line
At the top of /etc/rc.local and then reboot. I did this and the file was created after rebooting. |
This is a PowerBeam AC5 400 or do I misunderstand the node name? Could you send me the support data for this, preferably just after you rebooted the node - thanks. |
Right, it's a Powerbeam AC5 400 file is attached (just downloaded it prior to posting) |
I see this in your log file:
Which suggests /etc/rc.local was being run as expected. |
interesting. So the issue might that be rc.local is running BEFORE eth0 comes up? |
I'm not sure why it would do anything on this hardware anyway as it should not have a matching board id to trigger the ethtool command. |
Interestingly though, it looks like we might be able to remove this completely, as OpenWRT has fixed the driver issue which required this on some hardware. |
The problem is it is connected to a Cisco router than is a #$@#$*$# to work with and won't auto negotiate properly. Unfortunately, the node is in a difficult to reach site so we're kinda stuck with the Cisco router for now. When we manually run ethtool, the router becomes happy and we assumed the rc.local call should do that for us (it is there by default, no?) |
I just caught something "itouch"????? Let me check I didn't fudge the entry in rc.local Edit: Doesn't matter. Either way it does show rc.local did run |
Yes ... but as you note, it doesnt have the desired effect on eth0. The networking has changed substantially in the recent release, and clearly this code is no longer doing what it once did. I suspect, for our purposes at least, it's no longer required as the driver has been fixed. Once I get some confirmation from people with the appropriate hardware, I'll remove this. Which doesnt help your situation much. I'm not sure were best to put code which is guaranteed to run once the network configuration has been completed. |
I notice in the logs that the node appears to have successfully negotiated 100Mb full duplex with your switch. No idea what your switch thinks of course. |
Yes, switch not router. In any case, we have major route flopping through that node until we run ethtool after a reboot. Then it settles down |
I should note that any changes you make to /etc/rc.local will not survive an upgrade. |
Understand (that's been my experience up to this point!) |
If you put your ethtool at the end of /etc/rc.d/S99local it should happen very later in the boot process. |
Worth a try, thanks! |
Closing. /etc/rc.local is still executed and has not been deprecated. It appears to be executed earlier in the boot process than before. |
I notice that ethtool is being used to set eth0 to non auto negotiate and set speed to 100 Mbs.
This command does not work at boot as rc.local was depreciated
The text was updated successfully, but these errors were encountered: