Systemd on vivid beta

[Colin Law]

On 9 March 2015 at 12:29, Tom H <tomh0665 at gmail.com> wrote:
> On Mon, Mar 9, 2015 at 6:56 AM, Colin Law <clanlaw at gmail.com> wrote:
>>
>> Does anyone here know enough about systemd to answer a question?
>>
>> Vivid is changing over to it today.  I have some custom init.d scripts
>> dating back to before even upstart came along, which have been working
>> fine.  With the change to systemd should these just continue to work
>> ok or do I need to do anything?
>>
>> I ask because one of them is playing up.  I can go into more detail
>> but would like to know first whether it should just work.
>
> Sure.

That is what I hoped.  The problem is with shutdown, but only on power
down.  I can run
systemctl stop myservice.service
and it functions correctly, and I can start it again.  But if I
shutdown it does not seem to be getting the timing right.  My init.d
script starts

#! /bin/sh
### BEGIN INIT INFO
# Provides:          automount
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Automounts SAMBA shares
# Description:       Dynamically (un)mounts specific SAMBA shares.
### END INIT INFO

Which I thought should mean that it will complete the stop before
shutting down syslog, but I have littered logging through the script
and I see a variable number of these displayed in syslog before
syslogd quits.  Sometimes I do not even see the first one, which is
the first executable line in the script.  I inherited the script years
ago and don't know much about init scripting but the above looks ok,
and it works fine in upstart.

Am I doing something obviously silly?  Alternatively any suggestions
to analyse the problem further?

Colin

>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users