That's correct, at least for some wired devices with a system
connection. It's to ensure that restarting NM as part of a security
update or whatever does not interrupt network connectivity server-type
boxes.
I still don't get why people would want to use NetworkManager on servers
anyway.
For use on servers: because it means that you only have to learn one tool.
Also, why not? ;)
On 27 February 2010 08:30, Dominik George n...@naturalnet.de wrote:
That's correct, at least for some wired devices with a system
connection. It's to ensure that restarting NM as part of a security
The point you're missing here is that network manager solves a very real
problem with links going down after boot time and not automatically coming
back up when they're available again (Read as: laptop users). A daemon was
necessary to fix this and nothing like it had been done before. The design,
On 02/27/2010 11:05 AM, Graham Lyon wrote:
The point you're missing here is that network manager solves a very real
problem with links going down after boot time and not automatically
coming back up when they're available again (Read as: laptop users). A
daemon was necessary to fix this and
Using NM 0.8 + nm-applet 0.8 I hit the following situation - if -update
plugin method fails (for whatever reason - e.g. plugin is not able to
create necessary file) - no error is returned to user. Error is
correctly returned if creation of new system connection fails.
I start
