[arch-general] How to make wicd work under systemd?
I changed to systemd recently but wicd does not start when system boots as before. I add /etc/systemd/wicd.service typed as [Unit] Description=Wicd Network Manager Requires=syslog.target After=syslog.target Conflicts=NetworkManager.service [Service] Type=dbus BusName=org.wicd.daemon ExecStart=/usr/sbin/wicd ExecStop=/usr/sbin/wicd -k [Install] WantedBy=network.target Any solutions? Thanks Xin
On Mon, Jul 9, 2012 at 1:59 AM, Xin Zhao <sean.null@gmail.com> wrote:
I changed to systemd recently but wicd does not start when system boots as before.
I add /etc/systemd/wicd.service typed as
Units should be in /etc/systemd/system/.
Requires=syslog.target After=syslog.target
These are not needed anymore.
[Install] WantedBy=network.target
I think multi-user.target is traditional here... Don't forget to `systemctl enable` your unit, and verify it with `systemctl start` of course. -- Mantas Mikulėnas
In addition to the comments from Mantas: On Mon, Jul 9, 2012 at 12:59 AM, Xin Zhao <sean.null@gmail.com> wrote:
Conflicts=NetworkManager.service
This is usually not done You probably want to add: Wants=network.target Before=network.target That means that the network.target will become "active" once wicd is up and running, so other services can order themselves After=network.target. -t
...In other words, make it exactly like the "wicd.service" unit that Arch already ships in extra/wicd. Why did you write your own unit in the first place? `systemctl enable wicd.service` should be sufficient. -- Mantas Mikulėnas
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists So I decide to google and write it on my own.... On Mon, Jul 9, 2012 at 12:16 AM, Mantas Mikulėnas <grawity@gmail.com> wrote:
...In other words, make it exactly like the "wicd.service" unit that Arch already ships in extra/wicd.
Why did you write your own unit in the first place? `systemctl enable wicd.service` should be sufficient.
-- Mantas Mikulėnas
On Mon, Jul 9, 2012 at 1:28 AM, Xin Zhao <sean.null@gmail.com> wrote:
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
Sounds like wicd is already enabled. You can verify this with "systemctl status wicd.service". To start it, either reboot or do "systemctl start wicd.service". -t
Thank you, Mantas and Tom. Thanks again On Mon, Jul 9, 2012 at 12:37 AM, Tom Gundersen <teg@jklm.no> wrote:
On Mon, Jul 9, 2012 at 1:28 AM, Xin Zhao <sean.null@gmail.com> wrote:
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
Sounds like wicd is already enabled. You can verify this with "systemctl status wicd.service". To start it, either reboot or do "systemctl start wicd.service".
-t
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
So I decide to google and write it on my own....
So what would be the bare minimum unit file to add a commandline. I ask because polkit is rediculous to edit especially if you have to create policy from scratch such as on Fedora, POLKIT's HOME! Systemd doesn't look anywhere near that level of idiocy, but I still wonder how quickly a commandline could be added without pre-pregged unit files? I guess you can fall back to rc anyway? -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
On Mon, Jul 9, 2012 at 9:35 AM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
So I decide to google and write it on my own....
So what would be the bare minimum unit file to add a commandline. I ask because polkit is rediculous to edit especially if you have to create policy from scratch such as on Fedora, POLKIT's HOME! Systemd doesn't look anywhere near that level of idiocy, but I still wonder how quickly a commandline could be added without pre-pregged unit files?
What do you mean by "add a commandline"? If you want to debug your boot you can do "systemctl enable debug-shell.service" and this will be available on tty9 on next reboot. Not sure if that's what you want though...? -t
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
So I decide to google and write it on my own....
So what would be the bare minimum unit file to add a commandline. I ask because polkit is rediculous to edit especially if you have to create policy from scratch such as on Fedora, POLKIT's HOME! Systemd doesn't look anywhere near that level of idiocy, but I still wonder how quickly a commandline could be added without pre-pregged unit files?
What do you mean by "add a commandline"? If you want to debug your boot you can do "systemctl enable debug-shell.service" and this will be available on tty9 on next reboot. Not sure if that's what you want though...?
It's easy to add your own script to arches non systemd init system which may even be a one liner if your in a hurry and a few more lines to add pretty initialisation. Considering the author wishes all scripts to disappear I am just wondering what the minimum required to be written in a unit file is between the current init and systemd for a roll your own or missing service. Atleast systemd works eventually (after making multiple symlinks) and gives complete info. Haven't spent long but I still haven't got mythtv-backend to load after upgrading mythbuntu once. I'm thinking I'll just add it to rc.local. -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
On Mon, Jul 9, 2012 at 11:35 AM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
I write my own because "systemctl enable wicd.service" failed The error message is Failed to issue method call: File exists
So I decide to google and write it on my own....
So what would be the bare minimum unit file to add a commandline.
Since you decided /not/ to google and try writing one on your own, here's a two-liner. --- [Service] ExecStart=/usr/bin/xinetd -dontfork --- /usr/lib/systemd/system is full of examples, most of which look like: --- [Unit] Description=OpenLDAP server daemon [Service] Type=forking ExecStart=/usr/sbin/slapd [Install] WantedBy=multi-user.target ---
because polkit is rediculous to edit especially if you have to create policy from scratch such as on Fedora, POLKIT's HOME!
And this is related to systemd how exactly?
I guess you can fall back to rc anyway?
The initscripts-systemd package will add support for both rc.local and individual rc.d scripts. -- Mantas Mikulėnas
Since you decided /not/ to google and try writing one on your own, here's a two-liner.
You shouldn't need to Google to be sure of that. Thankyou for saving me more time than it cost you.
--- [Service] ExecStart=/usr/bin/xinetd -dontfork ---
I guess you can fall back to rc anyway?
The initscripts-systemd package will add support for both rc.local and individual rc.d scripts.
Cool so the statement from the design document. "So, let's get rid of shell scripts in the boot process!" Is more like reduce than get rid. In fact aside from the copying and symlinking it may be quicker than the current arch system to add a custom service. Though it may take longer to be sure of that initially :-). -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
On Mon, Jul 9, 2012 at 4:38 PM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
The initscripts-systemd package will add support for both rc.local and individual rc.d scripts.
Cool so the statement from the design document.
"So, let's get rid of shell scripts in the boot process!"
Is more like reduce than get rid. In fact aside from the copying and symlinking it may be quicker than the current arch system to add a custom service. Though it may take longer to be sure of that initially :-).
The intent is to get rid, completely, of the shellscripts currently in /etc/rc.d/ or /etc/init.d/, replacing them with native systemd units. However, it does not try to stop you from running arbitrary programs – shell scripts or not – as part of your boot process. If you write a unit to start /etc/rc.local or /etc/rc.d/yourdaemon, it won't complain – you just lose some of the advantages of systemd if you run all your daemons like that. -- Mantas Mikulėnas
participants (4)
-
Kevin Chadwick
-
Mantas Mikulėnas
-
Tom Gundersen
-
Xin Zhao