Owens, Stephen:
The start script calls other scripts to start two application
components and then the start script exits.
One of the application components also spawns a couple of child processes.
There ends up being two pid files, one for each component, describing
the state of the
Owens, Stephen:
UMask=0764
This is almost certainly wrong, by the way.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, 20.12.16 17:41, Owens, Stephen (MASSIT) (stephen.ow...@mass.gov) wrote:
> I'm stuck with 3rd party startup scripts.
>
> I was confused by the systemd-service documention for Type
> Type=
> If set to forking, it is expected that the process configured with
> ExecStart= will call
I'm stuck with 3rd party startup scripts.
I was confused by the systemd-service documention for Type
Type=
If set to forking, it is expected that the process configured with
ExecStart= will call fork() as part of its start-up
As far as I could see, the 3rd party scripts do not use fork.
On Tue, 20.12.16 17:10, Owens, Stephen (MASSIT) (stephen.ow...@mass.gov) wrote:
> [Service]
> Type=oneshot
> RemainAfterExit=yes
Type=oneshot is for services that run at boot and exit at
boot. i.e. stuff that generally doesn't stay around, stuff like fsck
or so which runs and exits before the
Hi,
I'm not sure if this is the correct list to ask this question, it's about
systemd unit configuration.
We have a 3rd party application that starts and stops via startup and shutdown
scripts which we would like to have start up automatically at linux boot time.
The start script calls other
