Am 27.10.2017 um 11:53 schrieb 清辰:
Where is the 'service xxx status' result stored? Or can I change the
service status manually, when start / stop the service outside of systemd
just don't start it outside systemd - yes it's really that easy
___
On Fr, 27.10.17 17:53, 清辰 (624001...@qq.com) wrote:
> Hi,
>
>
> Where is the 'service xxx status' result stored? Or can I change the
> service status manually, when start / stop the service outside of
> systemd.
PID 1 maintains a per-service record in its internal memory. Only
PID 1 itself
On Thu, 29.06.17 11:51, Oliver Neukum (oneu...@suse.com) wrote:
> Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
> >
> > Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
> > >
> > > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > > >
> > > > Well, it's
Am 29.06.2017 um 11:51 schrieb Oliver Neukum:
Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
Well, it's a service manager. As such it keeps track of
On Thu, Jun 29, 2017 at 11:51:53AM +0200, Oliver Neukum wrote:
> Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
> >
> > Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
> > >
> > > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > > >
> > > > Well, it's a
Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
Well, it's a service manager. As such it keeps track of services,
knows when they are started and when they aren't. Why would it stop
services that aren't started?
Because you
Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
>
> Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
> >
> > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > >
> > > Well, it's a service manager. As such it keeps track of services,
> > > knows when they
On Thu, 29.06.17 10:05, Oliver Neukum (oneu...@suse.com) wrote:
> Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > Well, it's a service manager. As such it keeps track of services,
> > knows when they are started and when they aren't. Why would it stop
> > services that
On Thu, Jun 29, 2017 at 10:05:08AM +0200, Oliver Neukum wrote:
> Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > Well, it's a service manager. As such it keeps track of services,
> > knows when they are started and when they aren't. Why would it stop
> > services that
Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> Well, it's a service manager. As such it keeps track of services,
> knows when they are started and when they aren't. Why would it stop
> services that aren't started?
Because you command it to do so.
The check systemd does
On Wed, 28.06.17 19:10, 清辰 (624001...@qq.com) wrote:
> Why? I think that will be more insured in case the status is not
> correct.
Well, it's a service manager. As such it keeps track of services,
knows when they are started and when they aren't. Why would it stop
services that aren't started?
11 matches
Mail list logo