On Nov 18 2016, Randy Rue <[email protected]> wrote:
> You mentioned believing I might be running some rebel version of systemd.
> Again, this is pretty stripped down install of CentOS_7 with:
> [root@fast-dr-proxy ~]# rpm -qa | grep systemd
> systemd-devel-219-19.el7_2.13.x86_64
> systemd-sysv-219-19.el7_2.13.x86_64
> systemd-python-219-19.el7_2.13.x86_64
> systemd-libs-219-19.el7_2.13.x86_64
> systemd-219-19.el7_2.13.x86_64
>
> Is one of these wrong?
I don't know.
> If I change the unit file to "Type=notify" with either version of mount.py
> (sd_notify imported or sd_notify = None), the service no longer starts via
> systemctl
Since you said it crashes when you don't set sd_notify = None, that's
not surprising. Or did you using the proper systemd module now?
> Right now I'm back to the stock mount.py and no Type argument in the unit
> file (which defaults me to simple). Back to where mounts and startups work
> but not shutdowns. But without any sd_notify call in umount.py, I believe
> this means that systemd is never hearing whether the umount completes?
I think as long as you use --fg, it should still work most of the time.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
