Systemd --user and network-online.target

I am trying to set up a user timer unit to whose service should be triggered only after the network has become online. The problem is that the network.target and network-online.target are system targets and not available for the --user daemon. Is there anyway to achieve this?

I wonder if you are on the right track using --user? The man page says this option is "of little use except for debugging".

Similar Messages

[Solved] systemd - network-online.target inactive dead

Still trying to get familiar with systemd after years with Ubuntu.
I have Crashplan installed and it's systemd service unit has the following line to wait until the network comes online.
After=network-online.target
However, this doesn't seem to be working. While trying to investigate this, I noticed that the target shows as 'inactive' and 'dead'. Not entirely sure what that means.
➜ ~ systemctl list-units --type=target --all | grep network-online
network-online.target loaded inactive dead Network is Online
Where can I go from here to make sure my Crashplan service only starts after the network is online?
Thanks.
Last edited by sajan (2015-04-21 22:18:14)

Head_on_a_Stick wrote:
Please post the output of:
systemctl status network-online.target
Do you actually have a working connection?
Well, I'm connected to the internet via Wifi by the time I get past my lightdm greeter. Not sure if systemd wants something else.
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=21.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=74.9 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 21.433/48.185/74.938/26.753 ms
➜ ~ systemctl status network-online.target
● network-online.target - Network is Online
Loaded: loaded (/usr/lib/systemd/system/network-online.target; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=19.3 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=24.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=3 ttl=54 time=19.2 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 19.243/20.992/24.429/2.435 ms
➜ ~
Last edited by sajan (2015-04-21 21:19:21)

[SOLVED] network-online.target is reached too early

Hi,
I want to start a systemd service once my wireless card is correctly set up (especially the wifi channel).
I think that the network-online is what I need.
So, I added the following lines at the beginning of my service file :
[Unit]
Description=...
Wants=network-online.target
After=network-online.target
However, it seems that the network-online.target is reached really early in the boot process, far before the discovery of the wireless card.
I don't know if it's important, but my wireless network is configured with netctl-auto.
I'm not very familiar with systemd, so I don't even understand how network-online.target is supposed to be notified that the network is online.
So, any help would be apreciated.
Thanks.
PS : I hope my approximative English is understandable enough.
Last edited by PHF (2013-10-28 02:51:43)

Lone_Wolf wrote:PHF, if i understand correctly you need to be sure the wireless connection is up and configured before the hostapd daemon runs ?
Yes, exactly.
Lone_Wolf wrote:a solution to achieve this might be to write a special command to check if the connection is up and add a service for it like the NetworkManager-wait-online.service .
This special command could be simple, like grepping the output op of ip addr show <interfacename> in a loop until it has a valid ip address.
Well, that's what I started to guess, without certitude : I need to manually order a waiting service before network-online.target.
I think my problem is solved now .
Meanwhile, I have found the ExecUpPost option for my netctl profiles.
It gives me the ability to execute a command once the connection is active.
So, I should be able to use it for unlocking my waiting service.
Thanks a lot for your help.

How to do a Clean Install (Don't preserve users and network settings)

I'd like to make a clean install of Snow Leopard -- but NOT erasing the whole drive and NOT migrating/preserving my users and network settings.
I have a bunch of applications and huge data sets (about 40G) on the boot drive that I don't want to go through the trouble of reinstalling or backing up, and that do not install Application Support folders and the like. I'd like to keep them, as well as migrate files like fonts and preferences over manually. Thus I don't want to format in disk utility and install.
I seem to remember there was the option in Tiger (Leopard maybe?) to Archive and Install Without Preserving anything, such as network settings, users, extensions and preferences. It would leave a completely fresh System, and a Previous System where I could manually migrate over everything I wanted to keep.
Is this possible in Snow Leopard?
Thanks.

Let me clarify.
Snow Leopard does an Archive and Install, BUT it PRESERVES Users and Settings. The default install "upgrades in place".
I have been having all sorts of weird crashes and hangs on my Leopard install and i want a fresh, not upgraded install.
I WANT to keep my old Leopard system so I can manually transfer over fonts, files, and applications.
I WANT an upgrade that DOES NOT preserve Preferences, Application Settings, extensions, etc. etc. etc.
But, I do NOT want to have to completely format and install, because that would involve burning approximately 60G of files and applications to DVD-Rs and copying them back.
Thanks.
Message was edited by: J Law

Unable to check "Preserve Users and Network Settings" checkbox

I may need to Archive and Install but I'm unable to select the "Preserve Users and Network Settings" checkbox when selecting Archive and Install. It's simply greyed out.
Any ideas?

Alan,
Try repairing disk and repairing permissions first. Then try the Archive and Install option again.
If that doesn't work you can always use a firewire drive and with carbon copy cloner, clone the drive. Then do a clean install and with the migration wizard import the users and network settings back. If you don't have firewire drive you can just do the Archive and Install without checking the "Preserver Users.." option. Your old users will still be in the "/Previous System/Users" folder.
Message was edited by: b3av1s

Cannot select Preserve Users and Network Settings

I am trying to do an Archive and Install but want to save my user settings but I cannot select "Preserve Users and Network Settings" as it is grayed out and unelectable. The question is, why?

Have a read of this.
http://discussions.apple.com/thread.jspa?threadID=1858697&tstart=1

Not given option to preserve users and network settings

I have a Quicksilver with Leopard installed. I've learned that normally you can't install Leopard on this computer because the processor (733 mhz) is too slow. It works, but I've found that it does indeed run poorly.(The hard drive was transferred from another computer, with Leopard already installed.)
So now I want to install Tiger on it, but when I get to the options installation window and click on the 'Archive and Install' button, the option to also 'preserve users and network settings' remains grayed out. I can't select it. Why so? I want to preserve the settings when I install Tiger.

zanzen wrote:
I have a Quicksilver with Leopard installed. I've learned that normally you can't install Leopard on this computer because the processor (733 mhz) is too slow. It works, but I've found that it does indeed run poorly.(The hard drive was transferred from another computer, with Leopard already installed.)
So now I want to install Tiger on it, but when I get to the options installation window and click on the 'Archive and Install' button, the option to also 'preserve users and network settings' remains grayed out. I can't select it. Why so?
because tiger installer doesn't know how to deal with leopard files as leopard was released after Tiger. downgraded like this is not recommended by apple.
I want to preserve the settings when I install Tiger.
you can't. however, if you do an archive and install without preserving user settings, your leopard home directory will be preserved in the Previous Systems folder at the top level of the hard drive. after you are done with the install of Tiger you can move what you need to your new home directory. move data files ONLY. don't move any preference files. they most likely won't work.
A better option would be to back up your data to an external and do an erase and install of tiger. you should make a backup anyway in case something goes wrong with the install.

Preserve Users and Network Settings

If I do an Archive & Install of my OS with this option off, will it keep my Users folder, or also erase it?
And would it do anything to it if I put the contents of my home folder in a new directory somewhere not in the Users folder?
Because I'd like to reset the network settings, but I'd like to keep my documents. Apple KBase tells that when this option is off, a backup is needed of your Users reason, but I don't see why if the documents are kept. Otherwise, I don't get why it's named "Archive" and Install, as nothing would be archived.

It won't erase it, but it will move it to the Previous System Folder, and because there are various permissions on all the thousands of files in your Users folder, it will be difficult to reset them all correctly. You're better off leaving the option on to Preserver Users and Network Settings.
Mulder

Preserve Users and Network Settings is grayed out

Hi, I was having some issues with my Mac so I decided to perform an archive and install. I currently have Snow Leopard 10.6.4. I popped in the disk but when I got to choosing install options, "Preserve Users and Network Settings" is grayed out. I want to keep all my data as it was and just reinstall Snow Leopard. Does this option appear later on in the installation? Is there a way to go back? It's currently installing Snow Leopard. Please help

Your Home folder may be in the Previous System Folder. Check to see if it's there and intact. Otherwise it's been moved into the new system. You need to make a backup of your Home folder on an external drive.
1. Boot from your Snow Leopard Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Complete the installation. In the Setup Assistant be sure to use a different username/shortname for the new admin account than you used before.
5. Upon completion use Migration Assistant in the Utilities folder to migrate your Home folder from the external backup drive.

Pulseaudio and systemd --user: DBus scope issues?

Hi,
I have a multi-seat setup, so I need user-wide pulseaudio and whatnot. I'm trying to setup my boot through systemd --user.
Testing audio working apps are firefox, mpv, and mpd. The problem is:
- If I start pulseaudio and mpd manually everything is fine (no use of systemd)
- If I start pulseaudio through systemd no application has sound.
- If I start pulseaudio and mpd through systemd only mpd has sound.
raimundoyamtech~$ cat .config/systemd/user/pulseaudio.service
[Unit]
Description=PulseAudio Sound System
After=sound.target
[Service]
ExecStart=/usr/bin/pulseaudio
[Install]
WantedBy=multi-user.target
raimundoyamtech~$ cat .config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd %h/.config/mpd/mpd.conf --no-daemon
ExecStop=/usr/bin/mpd %h/.config/mpd/mpd.conf --kill
Restart=always
[Install]
WantedBy=multi-user.target
If I add BusName=org.pulseaudio.Server to the pulseaudio.service nothing changes.
Using pulseaudio's autospawn=yes leads to what seems to be same behaviour: mpd by systemd starts pulseaudio and is the only app with sound.
./config/pulse/client.conf only contains default-sink. Everything else is default.
Using alsa alone is not an option because of firefox.
Any thoughts?
EDIT:
raimundoyamtech~$ systemctl --version
systemd 208
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
raimundoyamtech~$ pulseaudio --version
pulseaudio 4.0
Last edited by Raimundo (2013-10-23 10:08:13)

ewaller wrote:
Please do not bump. I understand the frustration; really, I do. But, these are very active forums with some very good technical people lurking about. I guarantee your post had been read. I read it. I did not have an answer, as I have never seen that behavior afore. I am certain that was true for many other regulars.
In the future, you can bring focus to a thread by providing more information.. Tell us what you have tried, what you have read since the last post, etc. At least it gives the impression that you are working the problem rather than merely waiting for a response.
I don't know almost anything about systemd, especially because it changes so rapidly and documention is so scarce and outdated that either I read the whole documentantion for my version in hopes of finding my problem (something for which I do not have time) or post a topic.
I posted everything I touched regarding systemd since the installation of my system, that's all the relevant information I know I can give, so at this point I had no more info to give.
Actually posting a topic is really my last resort, it usually means that I have already tried everything I knew and I'm hopeless already.
raimundoyamtech~$ loginctl list-sessions
SESSION UID USER SEAT
2 1002 carla seat0
1 1000 raimundo seat0
2 sessions listed.
raimundoyamtech~$ loginctl show-session 1
Id=1
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6670234
VTNr=1
TTY=tty1
Remote=no
Service=login
Scope=session-1.scope
Leader=1456
Audit=1
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050072367636
IdleSinceHintMonotonic=0
Name=raimundo
raimundoyamtech~$ loginctl show-session 2
Id=2
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6667439
VTNr=2
TTY=tty2
Remote=no
Service=login
Scope=session-2.scope
Leader=1453
Audit=2
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050025387636
IdleSinceHintMonotonic=0
Name=carla
raimundoyamtech~$ loginctl show-session 3
Failed to issue method call: No such file or directory
What is an active session? Oo Never heard of it
I could start things. Pulseaudio started, so did mpd. I also have a /usr/lib/systemd/systemd --user process started for each user. I assumed this would be it since this
raimundoyamtech~$ systemctl --user
Failed to issue method call: Process /bin/false exited with status 1
always happens and I've read that systemctl --user is no longer required.
[EDIT]
Fixed it. Don't remember where I read that it wasn't required, just that it was in the same place I found someone else complaining about getting this error.
For anyone else encountering this: sed -i s/system-auth/system-login/g /etc/pam.d/systemd-user
and systemctl --user will work. Insults fly out to the one who wrote it wasn't required!
Still am not able to get an active session though
[/EDIT]
Why would there be a need for anything else? I'm gonna check on that. Thanks!
See, the bump worked ^^ but ok I'll try to refrain from doing that next time. Sorry.
Last edited by Raimundo (2013-10-29 16:27:55)

Forward systemd's sleep.target to a systemd user session

My naive approach was the following:
[email protected]
[Unit]
Description=sleep.target of a systemd user session
Before=sleep.target
StopWhenUnneeded=yes
[Service]
Type=oneshot
User=%I
RemainAfterExit=yes
ExecStart=/usr/bin/systemctl --user start sleep.target
ExecStop=/usr/bin/systemctl --user stop sleep.target
[Install]
WantedBy=sleep.target
sleep.target
[Unit]
Description=Sleep Timer Target
StopWhenUnneeded=yes
Unfortunately I got the following error:
$ systemctl status user-sleep@joerg
[email protected] - sleep.target of a systemd user session
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Mo 2013-06-10 12:30:41 CEST; 43min ago
Process: 10503 ExecStart=/usr/bin/systemctl --user start sleep.target (code=exited, status=1/FAILURE)
Jun 10 12:30:41 turing-machine systemd[1]: Service [email protected] is not needed anymore. Stopping.
Jun 10 12:30:41 turing-machine systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jun 10 12:30:41 turing-machine systemd[1]: Failed to start sleep.target of a systemd user session.
Jun 10 12:30:41 turing-machine systemd[1]: Unit [email protected] entered failed state.
Can I use "systemctl --user" only at a login shell and not in a systemd unit? Because using "systemd --user" from tty works great.
My use case is to logout gajim before suspend. This cannot be done in a normal .service file, because it does require a connection to the current dbus session.

My naive approach was the following:
[email protected]
[Unit]
Description=sleep.target of a systemd user session
Before=sleep.target
StopWhenUnneeded=yes
[Service]
Type=oneshot
User=%I
RemainAfterExit=yes
ExecStart=/usr/bin/systemctl --user start sleep.target
ExecStop=/usr/bin/systemctl --user stop sleep.target
[Install]
WantedBy=sleep.target
sleep.target
[Unit]
Description=Sleep Timer Target
StopWhenUnneeded=yes
Unfortunately I got the following error:
$ systemctl status user-sleep@joerg
[email protected] - sleep.target of a systemd user session
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Mo 2013-06-10 12:30:41 CEST; 43min ago
Process: 10503 ExecStart=/usr/bin/systemctl --user start sleep.target (code=exited, status=1/FAILURE)
Jun 10 12:30:41 turing-machine systemd[1]: Service [email protected] is not needed anymore. Stopping.
Jun 10 12:30:41 turing-machine systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jun 10 12:30:41 turing-machine systemd[1]: Failed to start sleep.target of a systemd user session.
Jun 10 12:30:41 turing-machine systemd[1]: Unit [email protected] entered failed state.
Can I use "systemctl --user" only at a login shell and not in a systemd unit? Because using "systemd --user" from tty works great.
My use case is to logout gajim before suspend. This cannot be done in a normal .service file, because it does require a connection to the current dbus session.

[SOLVED] Getting my systemd user service to talk to dbus

I'm currently trying to set up a nice email workflow with mbsync, msmtp and notmuch.
My passwords are saved in the Gnome keyring "login", and I've configured mbsync to use secret-tool to retrieve them. Unfortunately when secret-tool is invoked from this systemd user service there is an error when it in turn tries to call dbus-launch.
Here is the error:
$ systemctl --user status -l mbsync.service
● mbsync.service - Synchronise IMAP folders
Loaded: loaded (/home/leo/.config/systemd/user/mbsync.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2015-05-10 20:10:56 BST; 17min ago
Process: 3691 ExecStart=/usr/bin/mbsync -a (code=exited, status=1/FAILURE)
Main PID: 3691 (code=exited, status=1/FAILURE)
May 10 20:10:55 think3 mbsync[3691]: (secret-tool:3696): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:55 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:55 think3 mbsync[3691]: Skipping account ymail, password command exited with status 1
May 10 20:10:56 think3 mbsync[3691]: (secret-tool:3698): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:56 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:56 think3 mbsync[3691]: Skipping account gmail, password command exited with status 1
May 10 20:10:56 think3 systemd[716]: mbsync.service: main process exited, code=exited, status=1/FAILURE
May 10 20:10:56 think3 systemd[716]: Failed to start Synchronise IMAP folders.
May 10 20:10:56 think3 systemd[716]: Unit mbsync.service entered failed state.
May 10 20:10:56 think3 systemd[716]: mbsync.service failed.
The file mbsync.service is simply
[Unit]
Description=Synchronise IMAP folders
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/mbsync -a
Any ideas how I can use secret-tool from within a systemd user service? The Wiki includes some information about DBus and systemd here but it looks a little outdated...
Last edited by curiousleo (2015-05-22 22:02:33)

barbae wrote:Please could you post the output of 'journalctl -b' just after user login into gnome through gdm?
Sure thing. Here it is (I've cut out some stuff that obviously had nothing to do with the problem at hand):
May 17 17:17:11 think3 systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
May 17 17:17:11 think3 systemd[1]: Created slice Root Slice.
May 17 17:17:11 think3 systemd[1]: Starting Root Slice.
May 17 17:17:11 think3 systemd[1]: Created slice System Slice.
May 17 17:17:11 think3 systemd[1]: Starting System Slice.
May 17 17:17:11 think3 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Reached target Login Prompts.
May 17 17:17:11 think3 systemd[1]: Starting Login Prompts.
May 17 17:17:11 think3 systemd[1]: Created slice User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Starting User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Reached target Slices.
May 17 17:17:11 think3 systemd[1]: Starting Slices.
May 17 17:17:11 think3 systemd[1]: Started Create System Users.
May 17 17:17:11 think3 systemd[1]: Created slice system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Starting system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Started Commit a transient machine-id on disk.
May 17 17:17:11 think3 systemd[1]: Started Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Starting Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Listening on D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Reached target Sockets.
May 17 17:17:11 think3 systemd[1]: Starting Sockets.
May 17 17:17:11 think3 systemd[1]: Reached target Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Login Service...
May 17 17:17:11 think3 systemd[1]: Starting Permit User Sessions...
May 17 17:17:11 think3 systemd[1]: Started D-Bus System Message Bus.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus...
May 17 17:17:11 think3 systemd[1]: Reached target Timers.
May 17 17:17:11 think3 systemd[1]: Starting Timers.
May 17 17:17:11 think3 systemd[1]: Started Permit User Sessions.
May 17 17:17:11 think3 systemd[1]: Starting GNOME Display Manager...
May 17 17:17:11 think3 systemd[1]: Started Login Service.
May 17 17:17:12 think3 systemd[1]: Started GNOME Display Manager.
May 17 17:17:12 think3 systemd[1]: Reached target Multi-User System.
May 17 17:17:12 think3 systemd[1]: Starting Multi-User System.
May 17 17:17:12 think3 systemd[1]: Reached target Graphical Interface.
May 17 17:17:12 think3 systemd[1]: Starting Graphical Interface.
May 17 17:17:12 think3 systemd-logind[293]: New seat seat0.
May 17 17:17:12 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
May 17 17:17:12 think3 systemd[1]: Reached target User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting Accounts Service...
May 17 17:17:13 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
May 17 17:17:13 think3 systemd[1]: Starting Authorization Manager...
May 17 17:17:13 think3 polkitd[443]: Started polkitd version 0.112
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /etc/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /usr/share/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Finished loading, compiling and executing 3 rules
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May 17 17:17:13 think3 polkitd[443]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 17 17:17:13 think3 systemd[1]: Started Authorization Manager.
May 17 17:17:13 think3 accounts-daemon[436]: started daemon version 0.6.40
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.Accounts'
May 17 17:17:13 think3 systemd[1]: Started Accounts Service.
May 17 17:17:13 think3 systemd[1]: Created slice user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting User Manager for UID 120...
May 17 17:17:13 think3 systemd-logind[293]: New session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Started Session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Starting Session c1 of user gdm.
May 17 17:17:13 think3 systemd[454]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
May 17 17:17:13 think3 systemd[454]: Unit type .busname is not supported on this system.
May 17 17:17:13 think3 systemd[454]: Reached target Paths.
May 17 17:17:13 think3 systemd[454]: Starting Paths.
May 17 17:17:13 think3 systemd[454]: Reached target Timers.
May 17 17:17:13 think3 systemd[454]: Starting Timers.
May 17 17:17:13 think3 systemd[454]: Reached target Sockets.
May 17 17:17:13 think3 systemd[454]: Starting Sockets.
May 17 17:17:13 think3 systemd[454]: Reached target Basic System.
May 17 17:17:13 think3 systemd[454]: Starting Basic System.
May 17 17:17:13 think3 systemd[454]: Reached target Default.
May 17 17:17:13 think3 systemd[454]: Startup finished in 3ms.
May 17 17:17:13 think3 systemd[454]: Starting Default.
May 17 17:17:13 think3 systemd[1]: Started User Manager for UID 120.
May 17 17:17:13 think3 gnome-session[460]: glamor: EGL version 1.4 (DRI2):
May 17 17:17:13 think3 org.a11y.Bus[459]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.Bus[459]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.atspi.Registry[518]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:14 think3 polkitd[443]: Registered Authentication Agent for unix-session:c1 (system bus name :1.9 [gnome-shell --mode=gdm --wayland --display-server], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:18 think3 gdm-password][674]: pam_unix(gdm-password:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[1]: Created slice user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting User Manager for UID 1000...
May 17 17:17:18 think3 systemd[1]: Started Session c2 of user leo.
May 17 17:17:18 think3 systemd-logind[293]: New session c2 of user leo.
May 17 17:17:18 think3 systemd[1]: Starting Session c2 of user leo.
May 17 17:17:18 think3 systemd[717]: pam_unix(systemd-user:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[717]: Unit type .busname is not supported on this system.
May 17 17:17:18 think3 systemd[717]: Started Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Starting Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Reached target default.target.
May 17 17:17:18 think3 systemd[717]: Startup finished in 13ms.
May 17 17:17:18 think3 systemd[717]: Starting default.target.
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Beginning session setup...
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: localuser:leo being added to access control list
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.a11y.Bus'
May 17 17:17:19 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.a11y.Bus'
May 17 17:17:19 think3 org.a11y.Bus[732]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.Bus[732]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.atspi.Registry[756]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
May 17 17:17:20 think3 polkitd[443]: Registered Authentication Agent for unix-session:c2 (system bus name :1.43 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:20 think3 gnome-session[734]: Entering running state
May 17 17:17:21 think3 gnome-shell[804]: GNOME Shell started at Sun May 17 2015 17:17:20 GMT+0100 (BST)
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'

[Solved] Starting systemd --user as a systemd --system process?

Hey guys,
I would like to run systemd --user as a system service using this .service file I wrote:
$ cat [email protected]
[Unit]
Description=Systemd --user instance for %I
Documentation=man:systemd
[Service]
User=%I
ExecStart=/usr/lib/systemd/systemd --user --log-level=debug
[Install]
WantedBy=multi-user.target
I enabled it for my user using `systemctl enable systemd-user@evan`, however, when starting it it fails with the following errors:
Jul 21 21:14:42 desktop systemd[12920]: systemd 204 running in user mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Jul 21 21:14:42 desktop systemd[12920]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system/[email protected]/[email protected]/systemd-12920.
Jul 21 21:14:42 desktop systemd[12920]: Failed to create root cgroup hierarchy: Permission denied
Jul 21 21:14:42 desktop systemd[12920]: Failed to allocate manager object: Permission denied
Is it possible to run systemd --user like this? Do I need to add something to my [email protected]?
Last edited by EvanPurkhiser (2013-07-22 02:10:10)

EDIT: I just realized that the systemd-user-session-units package will only include specific units at build-time weather I have have the programs or not. You're right, I should just use this package!
Well, to be honest, maybe I'm trying to hack around a problem that doesn't even really exist, but I don't think the systemd-user-sessions-units package meets my needs.
The way I would like to have my user sessions setup is something like this:
I would like to have an instance of systemd --user always running under my user so I can keep things like transmission-daemon always running, even when I don't have a user session open. When I do start my user session (via logging into getty) I want to bring my systemd instance up to a certain target. For example, logging in via tty1 should bring up graphical.target, which will start X11 and all that, while logging into any other tty will start console.target (for stuff like ssh-agent etc).
Thinking more about this I suppose there's really no reason I couldn't use the [email protected] from systemd-user-session-units, but since I won't use most of the other user units included, I would rather just not use it.
Here's what my .profile looks like:
if systemctl -q is-active systemd-user@evan
then
# Default systemd to the console target
target="console"
# If we're logging in from VT1 start the graphical target
if [[ $XDG_VTNR == 1 ]] && ! systemctl --user -q is-active graphical.target &> /dev/null
then
export DISPLAY=:0
target="graphical"
fi
# Set all environment variables in the systemd --user instance (still working on this)
env | systemctl --user set-environment -
# Bring up systemd --user to the specified target
systemctl --user start ${target}.target
fi
source "$HOME/.bashrc"
Last edited by EvanPurkhiser (2013-07-22 03:56:13)

[SOLVED] Question about systemd-user-session

Hi!
I'm trying to setup a systemd --user session (using user-session-units and xorg-launch-helper from aur).
I have a couple of questions; this is my .xinitrc now:
#!/bin/bash
export BROWSER=chromium
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
spacefm --desktop &
compton -cGCf -m 0.9 -i 0.8 -D 5 --shadow-exclude 'g:e:Conky' &
volumeicon &
/home/federico/Script/touchpadoff_onboot.sh &
#connman-ui-gtk &
/home/federico/Script/calised-script &
dimdaemon &
tint2 -c .config/tint2/dragonauta.tint2rc &
conky -p 5 -c Script/conky.conf &
exec openbox
1) is "if" statement required when using systemd-user-session? And if yes, how can I reproduce it?
2) "conky -p 5 " will wait 5 seconds doing nothing. Will this mean that other .service will wait for it to finish? (i guess no, since they're executed in parallel).
3) how can I export "chromium" as my default browser?
Thank you very much!
Last edited by nierro (2013-04-06 17:56:17)

I followed everything in that wiki, and in KaiSforza and sofar github page.
I finally managed to get my old method (autologin to vt and autostart x) to work together with systemd --user: i put in .xinitrc "systemd --user" and deleted everything else.
So, my .config/systemd/user/ works. The problem is in the [email protected], i guess. I configured it like wiki says, mind to post here your /etc/systemd/system/[email protected]?
Thanks.
EDIT: here it is my [email protected]:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
[Unit]
Description=User Manager for %I
After=systemd-user-sessions.service
# This is needed for folks running Xorg on vt/1
Conflicts=[email protected]
[Service]
User=%I
PAMName=login
# Note memory:/ required kernel memory CGroups support
ControlGroup=%R/user/%I/shared cpu:/ memory:/
ControlGroupModify=yes
Type=notify
TTYPath=/dev/tty1
ExecStart=-/usr/lib/systemd/systemd --user
Environment=DISPLAY=:0
Environment=XDG_RUNTIME_DIR=/run/user/%U
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/%U/dbus/user_bus_socket
[Install]
WantedBy=getty.target
and loginctl says my user has "1000" as UID.
Last edited by nierro (2013-04-05 16:13:14)

Start systemd --user once after first login, not per session?

Hey guys,
So I've been toying around with using systemd to manage user daemons and some oneshot processes, it seems like it could be really nice
Here's what I'm thinking I would like to do:
I would have two user targets, `console.target` and `graphical.target`.
The console target will start things like pulseaudio, ssh-agent (envoy), transmission, stuff like that.
The graphical target will start xorg and then other things like the WM, set the wallpaper.. you get the idea. Obviously the graphical target will want the console target.
Now, the part I wanted to get some feedback on is this: I would like a systemd --user instance to only be started once after my first login, not once per session.
So for example, I login from vt1 and it brings systemd --user up to the graphical.target. Then if I later SSH in from somewhere, it won't start a new systemd --user session (Ie, won't start pulse-audio, transmission-daemon, etc).
However, if I haven't logged into my machine yet and I SSH in, it will start up systemd --user and will start the console.target. If I then later login via vt1 it will see that there's already a systemd --user session started and start the graphical.target
Does this make sense? Is it a bad idea?

You could make a column in the database, and when the
information is set (emailed) make the value to be 0, then when they
first register use a IF recodset("column_name") = 0 Then
reponse.redirect("filloutpage.asp") end if, then when they fill out
the info have a hidden form field thats updates the value to 1. on
the login page after the first if make another IF
recordset("column_name") = 1 Then response.redirect("index.asp")
end if.
i have forms that have three different redirect based on user
input, and you could do the same thing you could add the one for
the first time to dw made code, here is an example, you could
change the request.form to a recordset value and it will work.
If Request.Form("select") = "Self" Then
MM_editRedirectUrl = "FridaySchedule.asp"
Response.Redirect(MM_editRedirectUrl)
End IF
If Session("MM_AdminEdit") = "True" Then
MM_editRedirectUrl = "FridayScheduleAdmin.asp"
Response.Redirect(MM_editRedirectUrl)
End IF
MM_editRedirectUrl = "FridayScheduleDept.asp"
If (Request.QueryString <> "") Then
If (InStr(1, MM_editRedirectUrl, "?", vbTextCompare) = 0)
Then
MM_editRedirectUrl = MM_editRedirectUrl & "?" &
Request.QueryString
Else
MM_editRedirectUrl = MM_editRedirectUrl & "&" &
Request.QueryString
End If
End If
Response.Redirect(MM_editRedirectUrl)

Systemd --user and network-online.target

Similar Messages

Maybe you are looking for