Given that they are in /etc/systemd isn't this just changing one
failure-when-on-a-different-filesystem for another?
John
=:->
On Mon, Apr 16, 2018 at 5:27 AM, Ian Booth <email address hidden> wrote:
> We can put the directories currently placed in /var/lib/juju/init into
> /lib/systemd/juju instead,
> The juju related symlinks in /etc/systemd/system would just be retargetted.
>
> We'll need an upgrade step to copy across existing service files.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1634390
>
> Title:
> jujud services not starting after reboot when /var is on separate
> partition
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1634390/+subscriptions
>
Given that they are in /etc/systemd isn't this just changing one when-on- a-different- filesystem for another?
failure-
John
=:->
On Mon, Apr 16, 2018 at 5:27 AM, Ian Booth <email address hidden> wrote:
> We can put the directories currently placed in /var/lib/juju/init into /bugs.launchpad .net/bugs/ 1634390 /bugs.launchpad .net/juju/ +bug/1634390/ +subscriptions
> /lib/systemd/juju instead,
> The juju related symlinks in /etc/systemd/system would just be retargetted.
>
> We'll need an upgrade step to copy across existing service files.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> jujud services not starting after reboot when /var is on separate
> partition
>
> To manage notifications about this bug go to:
> https:/
>