[systemd-devel] [Feature Request] systemctl --user status to output journal logs

with _SYSTEMD_OWNER_UID=myid in my logs but they do not correspond to messages generated by the services from systemd --user, so I don't really know what _SYSTEMD_OWNER_UID means :) Cheers! Damien Robert ___ systemd-devel mailing list systemd-devel

[systemd-devel] systemctl --user

allow to simulate OnExitExec= by putting it on StartLimitAction= and setting StartLimitBurst=1 and Restart=always, but it is probably not a good idea). -- Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http

Re: [systemd-devel] cannot start swap unit on lvm

Alexey Shabalin wrote in message CAEdvWkQTe1rZ=+artom3hfr6rc8qgvbf2mgqfx44k+erjhp...@mail.gmail.com: [Swap] What=/dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64 systemctl start dev-disk-by\x2duuid-a8ce6981\x2d1afd\x2d4af6\x2d8783\x2d784b3c7a7d64.swap cannot activate swap, error by

[systemd-devel] [Featur Request] Allow list of names in file.network

This is a minor feature request for systemd-networkd: my files in /etc/systemd/network/ all share the same pattern: [Match] Name=en* [Network] DHCP=yes [Match] Name=eth* [Network] DHCP=yes [Match] Name=usb* [Network] DHCP=yes I would like to be able to only write one file, like [Match]

[systemd-devel] [feature request] allow instances in file.preset

I really like the new preset directive, and I plan to use preset files to synchronise the services I launch at boot across my computers. However it is a bit cumbersome that preset files do not parse instanced services files. I could play with DefaultInstance in foobar@.service.d/ droplets and add

Re: [systemd-devel] [feature request] allow instances in file.preset

Damien Robert wrote in message m01rcj$dhh$2...@ger.gmane.org: I really like the new preset directive, and I plan to use preset files to synchronise the services I launch at boot across my computers. Also according to the man file systemd.preset and my test, while user systemd units are looked

Re: [systemd-devel] [feature request] allow instances in file.preset

never hacked systemd before. Would something like that be ok? (not tested, just to see if I am in the right direction) Thanks, Damien Robert -- 8 - From 7755e4afc3dc24f50c97c28fd7c00fd576d882cc Mon Sep 17 00:00:00 2001 From: Damien Robert

Re: [systemd-devel] [feature request] allow instances in file.preset

of the outer 'else if () {' and i was missing some brackets. Here is an updated patch, but I really need to test it inside a container first; I'll send you a real version asap. Thanks for your comments! -- 8 --- From: Damien Robert damien.olivier.robert+...@gmail.com

Re: [systemd-devel] [feature request] allow instances in file.preset

foo@bar.service in a preset rule works with systemctl preset-all. Maybe I missed something and it already works? Thanks, Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd

Re: [systemd-devel] [feature request] allow instances in file.preset

, I'll keep you updated]. Thanks, Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [feature request] allow instances in file.preset

-systemd.preset, the line enable getty@.service correctly enables getty@tty1.service -- Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [feature request] allow instances in file.preset

, Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [feature request] allow instances in file.preset

From Damien Robert, Fri 03 Oct 2014 at 19:18:31 (+0200) : From the preset file? I agree that since the enable/disable directive denotes glob, they are not well suited for instances services. Maybe add a new directive: instanciate foo@bar.service uninstanciate foo@bar.service

Re: [systemd-devel] Shell expressions in EnvironmentFile

Lennart Poettering wrote in message 20141008094838.GB26284@gardel-login: On Tue, 07.10.14 19:18, Simon Peeters (peeters.si...@gmail.com) wrote: ExecStart=/bin/sh -c . /something/that/sets/var; /some/file $var THis would certainly work, but I'd strongly advise to use exec for executing

Re: [systemd-devel] [feature request] allow instances in file.preset

From Lennart Poettering, Wed 08 Oct 2014 at 23:33:13 (+0200) : On Fri, 03.10.14 19:18, Damien Robert (damien.olivier.rob...@gmail.com) wrote: But this means it would only find the template, and the instance would have to come from somewhere else, but where? From the preset file

Re: [systemd-devel] [feature request] allow instances in file.preset

as a list of filenames, but only as something to match file names against... Yes, this is exactly what I was saying, sorry for the miscommunication... -- Damien Robert http://www.normalesup.org/~robert/pro ___ systemd-devel mailing list systemd-devel

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

Colin Guthrie wrote in message m1rf8b$ojg$1...@ger.gmane.org: I want to rely on systemd --user to handle PulseAudio's activation (ditching the built in stuff) and but I'm worried that e.g. GNOME or KDE might start up their own session stuff and spawn some PA consuming process before systemd

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

Lennart Poettering wrote in message 20141020173828.GA4509@gardel-login: They should probably adopt socket activation anyway, otherwise they'd be quite annoying on multi-user systems if lingering is used. I am brainstorming here, but would it make sense to add hooks to logind when a session is

[systemd-devel] systemd-journald watchdog timeout

On one boot I got a watchdog timeout on systemd-journald: Oct 21 20:08:21 feanor systemd-journal[213]: Permanent journal is using 68.7M (m Oct 21 20:08:21 feanor systemd-journal[213]: Time spent on flushing to /var is 2 Oct 21 20:08:25 feanor kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not

Re: [systemd-devel] systemd-journald watchdog timeout

From Lennart Poettering, Wed 22 Oct 2014 at 16:59:09 (+0200) : On Wed, 22.10.14 13:10, Damien Robert (damien.olivier.robert+gm...@gmail.com) wrote: That's difficult to say just from these logs. Yeah that was what I feared. Can you reliably reproduce this? If so, can you attach strace

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

://bugs.freedesktop.org/show_bug.cgi?id=78905 Wonderfull! The future is bright for user session :) With PA's socket activation, since mpd already has socket activation, the only thing I am still missing is ssh-agent socket activation! -- Damien Robert ___ systemd-devel

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

Zbigniew Jędrzejewski-Szmek wrote in message 20141019135812.gu29...@in.waw.pl: PAM creates sessions by calling into systemd's pam-module, which then uses CreateSession() (internal api!). This call does not return until the job of user@.service is done. `systemd --user` notifies READY=1

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

From Lennart Poettering, Thu 23 Oct 2014 at 11:49:27 (+0200) : On Thu, 23.10.14 08:09, Damien Robert (damien.olivier.robert+gm...@gmail.com) wrote: But isn't using default.target more flexible than basic.target? When basic.target is activated I expect at least socket.target, timers.target

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

to be launched. I was thinking of using a default.target with DefaultDependencies=false, so it does not even pull basic.target; not something that launch more things than basic.target. -- Damien Robert http://www.normalesup.org/~robert/pro ___ systemd-devel

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

From Zbigniew Jędrzejewski-Szmek, Thu 23 Oct 2014 at 17:26:57 (+0200) : order it after basic.target (which things are by default anyway)... My proposal now, (which is the same Damien's as I understood him): 1. pam_systemd should sync on default.target 2. by default default.target should

Re: [systemd-devel] Shell expressions in EnvironmentFile

From Lennart Poettering, Wed 08 Oct 2014 at 20:48:55 (+0200) : SyslogIdentifier= should do it. It works, thanks! See systemd.exec(5) for details. When I was looking for something like that in the doc, I was confused by this passage: This option is only useful when StandardOutput= or

Re: [systemd-devel] [Featur Request] Allow list of names in file.network

From Tom Gundersen, Thu 23 Oct 2014 at 20:14:45 (+0200) : Yes, this absolutely makes sense. Maybe even en*|usb*, like the udev logic. Happy to take a patch, but put on TODO for now. Great! I'll try to write a patch if I have the time! Thanks, Damien

Re: [systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

a long time, I was very impressed when I tried it and it worked out of the box); but having 'hooks' on logind would help a bit. But this is not really an important feature request for me, it was just an idea in passing. -- Damien Robert http://www.normalesup.org/~robert/pro

[systemd-devel] segfault in timesyncd

Here are the logs: Nov 06 16:14:56 numenor systemd[1]: Started Network Time Synchronization. Nov 06 16:14:56 numenor systemd-timesyncd[4881]: Using NTP server 10.3.255.254:123 (10.3.255.254). Nov 06 16:15:06 numenor systemd-timesyncd[4881]: Timed out waiting for reply from 10.3.255.254:123

Re: [systemd-devel] systemd user service when x is started

My plan is to use after X is started a second target, let's call it wm.target, with all services relevant to the X session. For now, I have no idea how to define After= It can't be right after the console.target as X need to be started first. I don't understand, if you start X manually, why

Re: [systemd-devel] systemd user service when x is started

' automatically. I put this command in my '.xprofile' (because the *DM usually source this file), and my .xinitrc contains [ -r $HOME/.xprofile ] . $HOME/.xprofile so it works with startx too. -- Damien Robert http://www.normalesup.org/~robert/pro ___ systemd

Re: [systemd-devel] Secret machine-id for RFC 7217 stable addresses

Tom Gundersen wrote in message : > If I understand correctly, most of the point of RFC7217 is achieved > even if the secret key is known. The important point is to have a good > hashing function, and in that case knowing the

[systemd-devel] slow uefi firmware/boot

I apologize for the out of topic question, but since systemd-analyze incorporate the firmware boot time I wonder if you may have any trick to share in order to improve it. Here is my boot timing (using systemd-boot and a lz4 compressed initrd): $ systemd-analyzed Startup finished in 14.156s

Re: [systemd-devel] Start a global service

Fair enough. But I don't really see the point to have a daemon that will just listen to udev events for power change (udevd does other things which I do not need). I prefer my solution which calls directly systemd services. Thanks, Damien Robert ___ sy

[systemd-devel] Start a global service

localuser:$(id -un) somewhere'). So I could try to find which user is using which X display and find their .Xauthority but it gets cumbersome. Thanks, Damien Robert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel