https://bugzilla.novell.com/show_bug.cgi?id=761316 https://bugzilla.novell.com/show_bug.cgi?id=761316#c1 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |markus.heinze@c-cron.de --- Comment #1 from Frederic Crozat 2012-06-01 14:37:41 UTC --- shutdown ordering is supposed to be the inverse of startup ordering. I've just tested here and openvpn was correctly started after network (at startup) and shutdown before network. could you try to boot with: systemd.log_level=debug systemd.log_target=syslog do a startup/shutdown cycle and attach /var/log/messages for this cycle ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761316 https://bugzilla.novell.com/show_bug.cgi?id=761316#c3 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |UPSTREAM --- Comment #3 from Frederic Crozat 2013-03-11 16:21:03 UTC --- We found a similar bug with our own vpn, due to a script run when openvpn is shutdown which run "rcfoobar restart" instead of "rcfoobar try-restart", causing the service to be always started and blocking the shutdown process. This will fixed for good with in Factory in the future, systemd upstream has added a special mode for shutdown to prevent this (but we can't backport it to released systemd, unfortunately). closing as upstream -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.