Software that tries to do too much (like systemd).

Does what it says on the tin IMO. It would be a proper pain to network on a laptop with wired connection when docked, wireless when not docked and then there are two different VPN standards that I need to switch between multiple times a day. Having it all in one place is more productive for me than having to deal with all the tools separately.

Sure, everything's is scriptable, but why should I duplicate the work that someone else has already done for me?

1 members found this post helpful.

Because at the end of this story, networkmanager will probably be that the only way to connect to the network (like it or not, have complex or not). As with systemd system startup.

Let's wait a couple of years to see if you still think the same.

as much as NM developers would love that (they are pretty open about it), it will never happen

the kernels "don't break userspace" means that while there is anybody in the world using some kernel interface, it will not be broken

wicd uses the interface, as is connman and iw/ip, as am i in this network manager i'm writing

1 members found this post helpful.

Yes, you're right, your reasoning applies equally well to systemd thing.

blancamolinos --

Let me fix that for you: Networkmanager is a evil thing on a Server ...

IMHNHO, of course.

This is why I think so ( YMMV ).

My Company supplies 'Linux Appliance Servers' to run our Integrated Software Solution to some of our Customers.

Almost all of the Appliances are Zotac ZBOXes running CentOS 6.x .

One thing we've learned to do is IMMEDIATELY Uninstall NetworkManager ( another of RedHat's Overreaching Tools from Hell ).

Firstly, because every time there's a glitch on one of the ethX ports, NM restarts the interface.

In addition, if you EVER remotely edit /etc/sysconfig/network/ifcfg-ethX while NM is running, you'll lose your SSH session and be locked out because NM helpfully reconfigures the Network 'instantly'.

... been there, done that ...

Nothing like a Server half-way across the USA which manages Networking the same way Networking is managed on a Windows Laptop

Our Boxen are Servers. The Server 'owns' the Static Network Interface. Not the user.

Again, IMNSHO, NM has no place on a Server.

Or maybe we're doing it wrong ?

-- kjh

2 members found this post helpful.

Network Manager is a great tool to manage multiple networks that you may need to connect to, especially wireless networks.

However, if you're only going to connect to one wired network, personally, I believe it is much easier to just set it up through your /etc/rc.d/rc.inet1.conf, at least on Slackware (I don't pretend to know how these things work on other distros).

But, I don't think there is any benefit (other than a very minor amount of hard drive space saved -- on 14.1, it is 9.6MB uncompressed) to uninstalling Network Manager. I still have it on my computers (both are configured using rc.inet1.conf), but I just leave rc.networkmanager as non-executable.

2 members found this post helpful.

Helpful ideas, bassmadrigal.

Thanks.

We uninstall Network Manager on our CentOS Boxes because we don't want a helpful local admin turning it on via the GUI when we're not watching <G>.

I only disabled /etc/rc.d/rc.networkmanager on my new SlackWare Current Laptop because it didn't work back in Feb when I installed Current.

I installed and activated wicd which DOES work for me.

There's been a NM update and I do use VPN Connections to reach a few Customer Boxen and if NM can manage VPN Connections, that would be worthwhile.

Maybe it's time to swap wicd and NM again on my Laptop and see if the new NM version 1.0.2 works now with my Killer Wireless 1535.

I'll post a followup.

Thanks again !

-- kjh

1 members found this post helpful.

Have you tried setting the plugin type from dhcpcd to dhclient?

1 members found this post helpful.

Hmmmm ... no but I will do that now <G>

Thanks ReaperX7 !

the stop service , no kill networkmanager, then if use "restart", and the start section he try to relaunch ... but stop not killed first.

and the more funny of all ,is when finally can killed (kde systemmanager) , if try to run NetworkManager on terminal , i can see how never start (root user)

but


sudo NetworkManager works.

why need sudo?

------
I develop a distro based on slackware (since years , is not new distro ) and need that working , but is not. (slackware 14.1 plays well with service stop /start /restart)
In my next release (14.2 based) , at the moment i migrate to wicd...because networkmanager script services are not working as expected...and im not see why.

Distro is network analizer focused, some tools need NO NETWORKING MANAGER app running , then need stop TOTALLY.
As i can say 14.1 works fine.

Thanks all try help.