confused by "inactive dead" syslog.target on fedora 20

[Robert P. J. Day]

  just digging into systemd (so be prepared for several potentially
silly questions), and i was playing with some variations of listing
systemctl services, and i ran:

# systemctl list-units -t target --all

and everything looked fine other than this line:

syslog.target          not-found inactive dead   syslog.target

  at the moment, syslog is running fine as a *service*, it seems ok
... so what does it mean that "syslog.target" is classified as
inactive and dead?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

[Ed Greshko]

On 02/05/14 16:33, Robert P. J. Day wrote:
>  On Wed, 5 Feb 2014, Ed Greshko wrote:
>
> > On 02/05/14 05:22, Robert P. J. Day wrote:
> >>   just digging into systemd (so be prepared for several potentially
> >> silly questions), and i was playing with some variations of listing
> >> systemctl services, and i ran:
> >>
> >> # systemctl list-units -t target --all
> >>
> >> and everything looked fine other than this line:
> >>
> >> syslog.target          not-found inactive dead   syslog.target
> >>
> >>   at the moment, syslog is running fine as a *service*, it seems ok
> >> ... so what does it mean that "syslog.target" is classified as
> >> inactive and dead?
> >>
> > Seems to me like a remnant.
> >
> > As you can see syslog.target does not exist and doesn't show up when
> > you do as suggested.
> >
> > systemctl list-unit-files -t target
> >
> > In F18, it did exist....
>     ,,, snip ...
>
>  so is this worth a bugzilla? it doesn't *hurt* anything, but if it's a
>  leftover, it's worth cleaning out.
>  
IMO, it couldn't hurt to file one.


-- 
Getting tired of non-Fedora discussions and self-serving posts

[Robert P. J. Day]

On Wed, 5 Feb 2014, Ed Greshko wrote:

>  On 02/05/14 05:22, Robert P. J. Day wrote:
>  >   just digging into systemd (so be prepared for several potentially
>  > silly questions), and i was playing with some variations of listing
>  > systemctl services, and i ran:
>  >
>  > # systemctl list-units -t target --all
>  >
>  > and everything looked fine other than this line:
>  >
>  > syslog.target          not-found inactive dead   syslog.target
>  >
>  >   at the moment, syslog is running fine as a *service*, it seems ok
>  > ... so what does it mean that "syslog.target" is classified as
>  > inactive and dead?
>  >
>
>  Seems to me like a remnant.
>
>  As you can see syslog.target does not exist and doesn't show up when
>  you do as suggested.
>
>  systemctl list-unit-files -t target
>
>  In F18, it did exist.... 
   ,,, snip ...

so is this worth a bugzilla? it doesn't *hurt* anything, but if it's a
leftover, it's worth cleaning out.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

[Ed Greshko]

On 02/05/14 05:22, Robert P. J. Day wrote:
>    just digging into systemd (so be prepared for several potentially
>  silly questions), and i was playing with some variations of listing
>  systemctl services, and i ran:
>
>  # systemctl list-units -t target --all
>
>  and everything looked fine other than this line:
>
>  syslog.target          not-found inactive dead   syslog.target
>
>    at the moment, syslog is running fine as a *service*, it seems ok
>  ... so what does it mean that "syslog.target" is classified as
>  inactive and dead?
>  
Seems to me like a remnant.

As you can see syslog.target does not exist and doesn't show up when you do as
suggested.

systemctl list-unit-files -t target

In F18, it did exist....

[egreshko@f18x system]$ uname -a
Linux f18x 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64
GNU/Linux
[egreshko@f18x system]$ locate syslog.target
/usr/lib/systemd/system/syslog.target
/usr/lib/systemd/system/syslog.target.wants

Looking at the F18 stuff.....

[egreshko@f18x system]$ rpm -q --whatprovides /usr/lib/systemd/system/syslog.target
systemd-201-2.fc18.7.x86_64
[egreshko@f18x system]$ more syslog.target
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# This unit file exists only for compatibility with broken unit files
# that express hard requirement dependencies on syslog.target (i.e.
# invalid usage of a provides-like target).

[Unit]
Description=Dummy Syslog target for compatibility with broken unit files
Documentation=man:systemd.special(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/syslog

# Avoid that we conflict with shutdown.target, so that we can stay
# until the very end and do not cancel shutdown.target if we should
# happen to be activated very late.
DefaultDependencies=no


Notice the Unit "Description".   I suppose they fixed the "broken unit
files" but some additional cleanup may be needed/coming.



-- 
Getting tired of non-Fedora discussions and self-serving posts