| Summary: | Flaky startup dependencies - maybe even bug | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | PetaMem R&D <info> |
| Component: | [OLD] baselayout | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** This bug has been marked as a duplicate of bug 266386 *** |
/etc/init.d/sshd has depend() { use logger dns need net } which I'd interpret as: we need "any network". Now my notebook can have eth0 or wlan0 (or both) up. Normally it starts up with eth0 up. I have written myself a "switch_net" script which looks like this: ------------------------------ #!/bin/bash WLAN_ACTIVE=`ifconfig | grep eth0` echo $WLAN_ACTIVE if [[ -z $WLAN_ACTIVE ]]; then echo 'wlan0 active - switching to eth0' /etc/init.d/net.eth0 start /etc/init.d/net.wlan0 stop exit 0 fi echo 'eth0 active - switching to wlan0' /etc/init.d/net.wlan0 start /etc/init.d/net.eth0 stop ----------------------------- I would expect that if wlan0 is up, I could restart sshd without hassle. Unfortunately no. ----------------------------- sol init.d # /etc/init.d/sshd restart * Bringing up interface eth0 * dhcp ... * Running dhcpcd ... dhcpcd[31187]: version 5.6.4 starting dhcpcd[31187]: eth0: waiting for carrier dhcpcd[31187]: timed out [ !! ] * ERROR: net.eth0 failed to start * ERROR: cannot start sshd as net.eth0 would not start ----------------------------- If I remember correctly, "need net" means "any net" so why is sshd still hooked to eth0? Reproducible: Always Actual Results: sshd fails to restart Expected Results: sshd should restart without hassle if I simply remove "need net" (crude hack), sshd restarts - and works - without hassle.