[systemd-devel] Randomly on shutdown, stop timeout for user at .service (repeated report, different user)

[Tom Gundersen]

On Fri, Oct 4, 2013 at 8:57 PM, Kok, Auke-jan H
<auke-jan.h.kok at intel.com> wrote:
> On Fri, Oct 4, 2013 at 9:37 AM, Toms Seisums <toms.seisums at gmail.com> wrote:
>> [object Object]
>
> Look at Gmail failing flat on its face... lol
>
> Aside from that, can you perhaps try this patch:
>
> --- systemd-user-sessions.service 2013-10-02 15:37:14.181330287 -0700
> +++ systemd-user-sessions.service 2013-10-04 11:53:37.023333867 -0700
> @@ -8,7 +8,7 @@
>  [Unit]
>  Description=Permit User Sessions
>  Documentation=man:systemd-user-sessions.service(8)
> -After=remote-fs.target
> +After=remote-fs.target dbus.service
>
>  [Service]
>  Type=oneshot
>
> some colleagues of mine identified that tasks in the user session that
> attempt to contact the system bus during shutdown may hang doing so.
> We can prevent this hang by making user sessions shut down entirely
> first before dbus is destroyed.
>
> It may or may not help. You can also insert After=dbus.service in to
> user at .service, but I feel this is a better spot.

This sounds reasonable (until kdbus is here ;) ).

However, should we perhaps take it one step further and order
dbus.service Before=basic.target to also cover stuff outside of user
sessions that may fall in its face when dbus goes away.

Cheers,

Tom