I can't reproduce this. I produces the errornous service by adding a
shell variable declaration to the .service file e.g.
[Unit]
Description=A service triggering an error
X=Y
env X=Y
[Service]
Environment=A=B
ExecStart=echo $A
[Install]
WantedBy=multi-user.target
I could trigger the failure by moving the file out of
`/lib/systemd/system` (to `/root`) and back, but I no longer have the
file. The failure seems to have occured due to the root filesystem being
corrupted by a failing `flashcache` write-back and the fact that I could
suppress the issue and recreate it (only once) a random correlation. I
no longer have the original file, but I'm sure it was correct besides
the variable declaration.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448656
Title:
systemd doesn't allow proper shutdown after it encountered errornous
.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448656/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
