Hi Ritesh,

Ritesh Raj Sarraf <r...@debian.org> writes:
> This does not seem to be the case, with the current version of systemd
> installed.
>
> Is systemd expected to take care of /etc/rc.local ???
Yes, systemd handles LSB sysvinit scripts, of which /etc/init.d/rc.local
is one (that script executes /etc/rc.local).

> -> Unit rc-local.service:
>       Description: /etc/rc.local Compatibility
>       Instance: n/a
>       Unit Load State: loaded
>       Unit Active State: failed
>       Inactive Exit Timestamp: Wed 2013-11-06 01:07:53 IST
>       Active Enter Timestamp: n/a
>       Active Exit Timestamp: n/a
>       Inactive Enter Timestamp: Wed 2013-11-06 01:07:53 IST
>       GC Check Good: yes
>       Need Daemon Reload: no
>       Name: rc-local.service
>       Name: rc.local.service
>       Fragment Path: /lib/systemd/system/rc-local.service
>       (null): /etc/rc.local
>       Condition Timestamp: Wed 2013-11-06 01:07:53 IST
>       Condition Result: yes
>       Requires: basic.target
>       WantedBy: multi-user.target
>       Conflicts: shutdown.target
>       Before: getty@tty1.service
>       Before: shutdown.target
>       Before: multi-user.target
>       After: network.target
>       After: systemd-journald.socket
>       After: basic.target
>       References: network.target
>       References: systemd-journald.socket
>       References: basic.target
>       References: shutdown.target
>       ReferencedBy: multi-user.target
>       ReferencedBy: getty@tty1.service
>       StopWhenUnneeded: no
>       RefuseManualStart: no
>       RefuseManualStop: no
>       DefaultDependencies: yes
>       OnFailureIsolate: no
>       IgnoreOnIsolate: no
>       IgnoreOnSnapshot: no
>       ControlGroup: cpu:/system/rc-local.service
>       ControlGroup: name=systemd:/system/rc-local.service
>       Service State: failed
>       Result: exit-code
>       Reload Result: success
>       PermissionsStartOnly: no
>       RootDirectoryStartOnly: no
>       RemainAfterExit: yes
>       GuessMainPID: yes
>       Type: forking
>       Restart: no
>       NotifyAccess: none
>       KillMode: control-group
>       KillSignal: SIGTERM
>       SendSIGKILL: yes
>       UMask: 0022
>       WorkingDirectory: /
>       RootDirectory: /
>       NonBlocking: no
>       PrivateTmp: no
>       ControlGroupModify: no
>       ControlGroupPersistent: yes
>       PrivateNetwork: no
>       IgnoreSIGPIPE: yes
>       LimitNOFILE: 4096
>       StandardInput: null
>       StandardOutput: journal
>       StandardError: inherit
>       SyslogFacility: daemon
>       SyslogLevel: info
>       -> ExecStart:
>               Command Line: /etc/rc.local start
>                       PID: 2966
>                       Start Timestamp: Wed 2013-11-06 01:07:53 IST
>                       Exit Timestamp: Wed 2013-11-06 01:07:53 IST
>                       Exit Code: exited
>                       Exit Status: 2
>       SysVStartPriority: 99
>From this I take it that systemd tried to run the init script, but the
init script returned with exit code 2. To get more information about it,
see “systemctl status rc.local.service”.

In case you still have questions, please also attach the output of
“systemctl status rc.local.service” and “journalctl -b”. Otherwise,
please close this bugreport.

-- 
Best regards,
Michael


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to