Your message dated Wed, 23 Mar 2016 17:22:08 -0300
with message-id
<caafdzj_iwpbq5zgbovei148wskxfxbksk2kqp6zbokux1lq...@mail.gmail.com>
and subject line Re: Bug#819040: insserv: Symlinked init script in
/etc/init.d/<service> fails to be recognised on reboot.
has caused the Debian Bug report #819040,
regarding insserv: Symlinked init script in /etc/init.d/<service> fails to be
recognised on reboot.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
819040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819040
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: insserv
Version: 1.14.0-5
Severity: normal
Dear Maintainer,
If an init script is symlinked to /etc/init.d/<NAME> and a call is made to
`update-rc.d' the init script will function correctly for the remainder of
the uptime of that machine.
Once the machine has restarted a call to start the service results in:
Failed to start <name>.service: <NAME> <name>.service failed to load: No such
file or directory.
This can be resolved by instead copying the init script and reissuing
`update-rc.d'.
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages insserv depends on:
ii libc6 2.19-18+deb8u3
insserv recommends no packages.
Versions of packages insserv suggests:
pn bootchart2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 23 March 2016 at 11:27, Brett Ryan <[email protected]> wrote:
>
>
> On 23 Mar 2016, at 22:05, Felipe Sateler <[email protected]> wrote:
>
> On Wed, 23 Mar 2016 18:52:20 +1100 Brett Ryan <[email protected]> wrote:
>>
>> > On 23 Mar 2016, at 18:39, Petter Reinholdtsen <[email protected]> wrote:
>> >
>> > When that is said, I suspect it is in general a good idea to not use
>> > symlinks in /etc/init.d/.
>>
>> I would generally agree, I'm presently setting up VM with a preinstalled
>> service in /opt running as its own user. When this service updates itself
>> it will only have access to the service location in /opt/<name> and
>> /srv/<name>, if I need to update the init script then I can do so in this
>> manner.
>
> Is /opt mounted in a separate partition?
>
>
> Indeed, it is.
I think there is nothing to do then: services and init scripts need to
be available first thing during boot, and for that you need to have
them available in / or /usr filesystems (or anything mounted from the
initrd, really).
Closing.
--
Saludos,
Felipe Sateler
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
