This bug was fixed in the package systemd - 229-4ubuntu4
---
systemd (229-4ubuntu4) xenial; urgency=medium
* 73-special-net-names.rules: Further refine ibmveth naming.
-- Martin Pitt Tue, 12 Apr 2016 12:06:30
+0200
** Changed in: systemd (Ubuntu)
Status: Fix Committed =>
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1563590
Title:
1.25.4, xenial, init script insta
Fix sent upstream in https://github.com/systemd/systemd/pull/3016 . This
is only cosmetical, thus setting importance to "Low".
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: juju-core
Status: New => Invalid
--
You received this bug notification because you
Sorry, the first part of my advice in #5 was wrong. "systemctl enable
foo.service" is not allowed if /etc/systemd/system/foo.service is a
symlink (This currently causes the "too many levels of symbolic links"
error, which is a crap message and we'll fix that).
So my revised advice is to just drop
However, at least for me the enablement actually works, I do get both
symlinks created. Just after that I get that (wrong) error message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
> /bin/systemctl link
> '/var/lib/juju/init/jujud-machine-0/jujud-machine-0.service'
> /bin/systemctl enable
> '/var/lib/juju/init/jujud-machine-0/jujud-machine-0.service'
This is redundant. Either use link like that and enable with just
"jujud-machine-0.service" (link already created the syml
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1563590
Title:
1.25.4, xenial, init script ins
7 matches
Mail list logo