| Summary: | support scripting/hooks | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | David Bremner <bremner-keyword-kde.673b66> |
| Component: | Control Module | Assignee: | Lamarque V. Souza <lamarque> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | kde, lamarque, rajeeshknambiar, yorirou |
| Priority: | NOR | ||
| Version: | 0.7 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | example script to snoop dbus and run user hooks on NM events | ||
Created attachment 22535 [details]
example script to snoop dbus and run user hooks on NM events
Good idea, 2 comments about the implementation: *) KDE 4 abstracts out NetworkManager so it can run on platforms that don't use it. The events emitted by Solid::Networking that wrap NM events are portable triggers. *) An increasing number of apps have event driven user scripting interfaces. Amarok, Kopete, and now KNetworkManager. An elegant way to do this at a desktop level would be to have a single dispatcher process on the desktop that listens to the bus and starts a script, but provides an API for individual apps to access and modify 'their' scripts. Consider KNotify as an example of this centralised but locally configurable architecture. You could use a graphical dbus client like qdbusviewer as a base for this. *** This bug has been confirmed by popular vote. *** *** Bug 166090 has been marked as a duplicate of this bug. *** You can use notifications to execute your scripts. We already have notifications that run before the connection is established (Establishing Network Connection), after it is established (Network Connection Succeeded) and after the connection is closed (Network Connection Disconnected). We just need to implement the one to be executed before disconnections. Well, using KNotification always works for user connections, but for system connection it only works if kded is running. To run scripts on all events we need to add the support for it to NM itself. There is an upstream bug already requesting this feature: https://bugzilla.gnome.org/show_bug.cgi?id=647068 Reassign Network Management bugs to new maintainer. Have a lot of fun, Lamarque! Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug. Please test again with the latest version and file a new bug in plasma-nm. Thank you! |
Version: (using KDE KDE 3.5.8) Installed from: Debian testing/unstable Packages OS: Linux Like several people out there, I wanted to have user (non-root) scripts run when NM changed state. I decided to write a quick python script to snoop the dbus, and call a function when an interface is brought up or down. Maybe somebody else will find this useful. Instead of a director of scripts, just place a file called .nmdispatchrc in the home directory, containing python code which defines functions ifup and ifdown. e.g. def ifup(interface,*args) print 'interface '+interface 'brought up' def ifdown(interface,*args) print 'interface '+interface+ ' brought down' It was suggested by Dan Williams that this functionality (or something similar) might be built in to the front end applet. What do you think?