nmcli regression regarding queries.....
I have identical laptops.. on the first running nmcli 0.9.9.0-46.git20131003.fc20 the command nmcli c show active gives me the current active connection(s) however on 2nd machine with later version nmcli 0.9.10-4.git20140704.fc21 the command nmcli c show active gives me "Error active - no such connection profile" Has there been a major change in nmcli output and structure as I've written quite a few scripts in etc/NetworkManager/dispatcher.d and re-writes would be a bit of a pain. Thanks ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nmcli regression regarding queries.....
On Fri, 2014-12-12 at 08:04 +, Another Sillyname wrote: > I have identical laptops.. > > on the first running > > nmcli 0.9.9.0-46.git20131003.fc20 > > the command > > nmcli c show active > > gives me the current active connection(s) > > however on 2nd machine with later version > > nmcli 0.9.10-4.git20140704.fc21 > > the command > > nmcli c show active > > gives me "Error active - no such connection profile" > > Has there been a major change in nmcli output and structure as I've > written quite a few scripts in etc/NetworkManager/dispatcher.d and > re-writes would be a bit of a pain. > Yes, that changed. >> nmcli connection show is now what >> nmcli connection show configured used to be. and >> nmcli connection show --active was >> nmcli connection show active I understand that this change breaks your scripts and it's a major annoyance. For what it's worth, non breaking compatibility is very important to us -- usually. In this case we changed it because this syntax makes more sense and you only find the old syntax in Fedora20. There was never a stable release with the old behavior and to my knowledge no other distribution got it. sed 's/nmcli connection show configured/nmcli connection show/g' sed 's/nmcli connection show active/nmcli connection show --active/g' Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
The short road to 1.0 (ANN: 0.995 released)
Hi everyone! The 1.0 release is imminent. We've been cleaning out the 1.0 tracker bug [1] for more than a month. With your help we'll get there next week! A holiday present for everyone! The 1.0 release will be huge step forward in functionality, cooperation, client APIs, configurable routing, nmcli/nmtui, DHCP, IPv6, reduced footprint, and tons more. It just doesn't stop. I'm looking forward to 1.0 and I hope you are too! I've branched git master for 1.0 and released 0.995/1.0-rc1 tarballs. Hammer on these so we can make 1.0 as solid as ever. Please file bugs at bugzilla.gnome.org, or drop by #nm on freenode. Let's get this done. http://ftp.gnome.org/pub/gnome/sources/NetworkManager/0.995/NetworkManager-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/network-manager-applet/0.995/network-manager-applet-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/NetworkManager-openconnect/0.995/NetworkManager-openconnect-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/NetworkManager-openswan/0.995/NetworkManager-openswan-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/NetworkManager-openvpn/0.995/NetworkManager-openvpn-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/NetworkManager-pptp/0.995/NetworkManager-pptp-0.995.0.0.tar.xz http://ftp.gnome.org/pub/gnome/sources/NetworkManager-vpnc/0.995/NetworkManager-vpnc-0.995.0.0.tar.xz Thanks, Dan [1] https://bugzilla.gnome.org/showdependencytree.cgi?id=682947 ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Cycle between logind and NetworkManager in case of remote user database
NetworkManager sets logind inhibitor lock to monitor for suspend events. So it implicitly requires logind to be present when NM starts. logind is ordered after nss-user-lookup.target. If we have remote user database, it means that logind depends on network to be up and running. If network is provided by NetworkManager we have a loop. Due to the fact that NetworkManager service itself does not declare dependency on logind, it can be pretty hard to recognize. Any idea how it can be solved nicely? I can only think of delaying inhibitor logic in NM until logind is started. Not sure what side effects it may have. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
