| 1 |
On Thu, Dec 19, 2013 at 2:50 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Wed, 18 Dec 2013 20:07:16 -0500, gottlieb@×××.edu wrote: |
| 3 |
> |
| 4 |
>> Switched to systemd and all was well for weeks. |
| 5 |
>> Then failure occurred (non-global ctrl_ifname). |
| 6 |
>> Tried network-manager (NM) with no success. |
| 7 |
>> |
| 8 |
>> New. |
| 9 |
>> Canek told me off-list that, when using NM, you don't enable dhcpcd, |
| 10 |
>> NM handles it all. Poof and when the smoke cleared ... |
| 11 |
> |
| 12 |
> The same applies to Wicd, the default systemd config appears to have |
| 13 |
> broken both in the same way. Maybe something should be added to the |
| 14 |
> systemd wiki page to cover this. |
| 15 |
|
| 16 |
The systemd default config is OK; if I'm not mistaken, Allan manually |
| 17 |
enabled both NM and dhcpcd (and, at the time, wicd and dhcpcd). There |
| 18 |
is no (reasonable) way for systemd to know that this is broken; if you |
| 19 |
enable both apache2 and lighttpd, without using socket activation, the |
| 20 |
one that starts second will fail since the first one will grab port |
| 21 |
80. Again, nothing that systemd (nor OpenRC, nor any other init |
| 22 |
system) can do about it. |
| 23 |
|
| 24 |
Regards. |
| 25 |
-- |
| 26 |
Canek Peláez Valdés |
| 27 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 28 |
Universidad Nacional Autónoma de México |
Archives