On Wed, 29 Oct 2014 20:17:19 -0700 "Patrick Burroughs (Celti)" <celticmadman@gmail.com> wrote:

On Wed, Oct 29, 2014 at 8:08 PM, Genes Lists <lists@sapience.com> wrote:

...

Work around is to add these 2 lines to /etc/systemd/system/stunnel.conf before the ExecStart line:

ExecStartPre=-/usr/bin/mkdir /run/stunnel ExecStartPre=/usr/bin/chown -R stunnel:stunnel /run/stunnel

Shouldn't that rather be handled by a tmpfiles.d snippet, and not in the service file?

Regards, ~Celti

Yes, tmpfiles is the correct way of handling this and there is already a conf file installed by stunnel that should be creating this dir. If it's not, the OP needs to look into why.

Genes Lists <lists@sapience.com> on Thu, 2014/10/30 08:23:

2) There is a tmpfiles snippet:

# cat /usr/lib/tmpfiles.d/stunnel.conf d /var/run/stunnel 0770 stunnel stunnel -

3) So the question now is why was /run/stunnel not created at boot?

journal only has this reference to tmpfiles:

Did not check, but... Possibly /var/run is no longer linked to ../run? You should change the path in /usr/lib/tmpfiles.d/stunnel.conf from "/var/run/stunnel" to "/run/stunnel". -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}

Genes Lists <lists@sapience.com> on Thu, 2014/10/30 08:52:

On 10/30/2014 08:27 AM, Christian Hesse wrote:

...

Possibly /var/run is no longer linked to ../run? You should change the path in /usr/lib/tmpfiles.d/stunnel.conf from "/var/run/stunnel" to "/run/stunnel".

I did check that and /var/run is indeed linked to /run.

Or it creates /var/run/stunnel, then removes /var/run to link it against ../run? I would suggest to fix pathes, then try again. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}

On 10/30/2014 12:04 PM, Tobias Hunger wrote:

Hi there,

tmpfiles.d is not the right approch: There is the RuntimeDirectory keyword for unit files to manage that directory. See http://www.freedesktop.org/software/systemd/man/systemd.exec.html for details.

The advantage of this keyword is that systemd makes sure that it is pristine whenever the service is started.

Maybe your stunnel unit is already using this? That would explain why the directory is gone (when the service is not running at least).

Hi The stunnel package from community does not include that variable nor does it include the user,group which would be necessary as well I would think. I'm still perplexed what systemd 217 did to trigger this being an issue now. Anyway here's what I see: $ cat /usr/lib/systemd/system/stunnel.service [Unit] Description=SSL tunnel for network daemons After=syslog.target [Service] ExecStart=/usr/bin/stunnel Type=forking [Install]