Re: [systemd-devel] systemd prompts for luks key, but keyfile provided in crypttab

2015-07-24 Thread Jan
Alex geosmin104 at gmail.com writes: I was advised on IRC to post this issue here after trying IRC, forums, searches, man pages, wikis, etc. During init, systemd asks for the passphrase of non-root LUKS drives when they are added to crypttab even though a keyfile is specified. The keyfile

Re: [systemd-devel] [ANNOUNCE] systemd-223 around the corner

2015-07-24 Thread Colin Guthrie
David Herrmann wrote on 23/07/15 16:28: Hi Following our ~2 week release plans, we intend to release v223 early next week. If anyone has open issues that need to be resolved before a release, please speak up. Right now, the changes consist of mostly bugfixes and a few configuration

Re: [systemd-devel] How to properly write an umbrella unit

2015-07-24 Thread Krzysztof Kotlenga
Lennart Poettering wrote: Daurnimator wrote: Lennart Poettering wrote: Maybe we can change the manager core to propagate Reload() calls for unit type that do not support it natively to other units listed in PropagateReloadsTo= and then become a NOP. Or in other words: invoking reload on a

[systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
Hi, I'm in the process of adding systemd native sockets to a service (rather than using inetd compatibility) and am trying to get my head around the proper way to configure the unit files so that the socket is optional rather than required but allowing restarting of the socket unit.

Re: [systemd-devel] How to properly write an umbrella unit

2015-07-24 Thread Lennart Poettering
On Fri, 24.07.15 11:07, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote: Unfortunately one cannot specify ConsistsOf in a unit file, which is a really annoying limitation. That limitation exists for a reason: systemd loads unit files lazily: only units that are referenced by some other unit are

Re: [systemd-devel] [ANNOUNCE] systemd-223 around the corner

2015-07-24 Thread Lennart Poettering
On Fri, 24.07.15 09:39, Colin Guthrie (gm...@colin.guthr.ie) wrote: David Herrmann wrote on 23/07/15 16:28: Hi Following our ~2 week release plans, we intend to release v223 early next week. If anyone has open issues that need to be resolved before a release, please speak up.

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread Dimitri John Ledkov
On 24 July 2015 at 10:38, James Hogarth james.hoga...@gmail.com wrote: I want a user to be able to systemctl start sslh and use listening addresses in /etc/sslh.cfg as always (so I'm reluctant to put a straight Sockets= in the service unit file) but as it stands the lazy You can write a

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
On 24 July 2015 at 10:38, James Hogarth james.hoga...@gmail.com wrote: Hi, I'm in the process of adding systemd native sockets to a service (rather than using inetd compatibility) and am trying to get my head around the proper way to configure the unit files so that the socket is optional

Re: [systemd-devel] Completion of error handling

2015-07-24 Thread Lennart Poettering
On Fri, 24.07.15 15:10, SF Markus Elfring (elfr...@users.sourceforge.net) wrote: An analysis script can point more source code places out for further considerations. Would you like to care for corresponding open issues? We are making heavy use of Coverity already on a daily basis, I think we

Re: [systemd-devel] Completion of error handling

2015-07-24 Thread SF Markus Elfring
I have no understanding of Coccinelle. This software provides the tool spatch which lets you specify transformations for C source code in a similar way you are used to already by the reuse of unified context diffs. http://coccinelle.lip6.fr/ I assume that you have eventually noticed specific

Re: [systemd-devel] How to properly write an umbrella unit

2015-07-24 Thread Krzysztof Kotlenga
Lennart Poettering wrote: On Fri, 24.07.15 11:07, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote: Unfortunately one cannot specify ConsistsOf in a unit file, which is a really annoying limitation. That limitation exists for a reason: systemd loads unit files lazily: only units that are

Re: [systemd-devel] systemd prompts for luks key, ?but keyfile provided in crypttab

2015-07-24 Thread Lennart Poettering
On Fri, 24.07.15 06:45, Jan (medhe...@web.de) wrote: My best guess is the different handling of the keyfile itself. Afaik, systemd-cryptsetup will use the full keyfile to open. That includes any trailing new line. Depending on how you use cryptsetup, it will handle they keyfile differently

Re: [systemd-devel] Completion of error handling

2015-07-24 Thread Lennart Poettering
On Fri, 24.07.15 18:15, SF Markus Elfring (elfr...@users.sourceforge.net) wrote: Generally, please be specific, provide patches. I suggest to consider additional patch formats as a better preparation for software improvements. We accept contributions only in git-format-patch frmatted

Re: [systemd-devel] systemd prompts for luks key, but keyfile provided in crypttab

2015-07-24 Thread Lennart Poettering
On Thu, 23.07.15 17:29, Alex (geosmin...@gmail.com) wrote: I was advised on IRC to post this issue here after trying IRC, forums, searches, man pages, wikis, etc. During init, systemd asks for the passphrase of non-root LUKS drives when they are added to crypttab even though a keyfile is

[systemd-devel] Session management for Systemd-native PulseAudio apps [was: Re: Packaging systemd user-instance service files]

2015-07-24 Thread Ahmed S. Darwish
Hi Colin, Thanks __a lot__ for your very informative reply! I was just going to cross-post this issue to the relevant PulseAudio channels, but it seems the PulseAudio folks are already here ;-) The main issue is indeed the combination of Systemd + PA user session management. Kindly find the

[systemd-devel] fstab generator and nfs-client.target

2015-07-24 Thread Rich Freeman
I noticed that mount units for nfs shares created by the generator do not Want=nfs-client.target or similar. That means that if you don't explicitly want nfs-client in your configuration then nfs shares will get mounted, but services like rpc-statd-notify.service won't run. Would it make sense