Bug#826041: Bug#816391: tor: "systemctl status tor" does not provide useful output

[Luca Boccassi]

Control: close -1

On Mon, 12 Feb 2018 00:54:00 +0000 Gabriel Filion <gabster at lelutin.ca>
wrote:
> On Wed, 1 Jun 2016 19:13:26 +0000 Peter Palfrader <weasel at debian.org>
wrote:
> > Michael Biebl schrieb am Donnerstag, dem 14. April 2016:
> > > Am 14.04.2016 um 00:46 schrieb Michael Biebl:
> > > > The tor.service afaics is only used, so you have a
> > > > systemctl restart/reload tor
> > > > shortcut which propagates that request to all instances.
> > > > tor.service in itself does not provide any service.
> > > > 
> > > > So it is useful to have.
> > > 
> > > I'm not sure. Maybe we can convince upstream that using "status"
on a
> > > service which is composed by several sub-services via PartOf [0],
also
> > > propagates the status request and merges that into a single
output.
> > > 
> > > Or we add a dedicated key, like PropagatesReloadTo [1], say
ProgatesStatusTo
> > 
> > Something like that might be nice indeed.  Cloning/etc bug.
> 
> It could be status propagation, or if upstream changes the status of
the
> "parent service", another idea could be to list all sub-services
> (instance names) in the output. maybe showing a one line status for
all
> instances would make the top-level status all the more useful.
> 
> I don't know much about the systemd code though so I don't know which
> option is more feasible. I just wanted to add in a different
suggestion
> for how to improve status output.

This is tracked upstream, there are no patches nor configuration
downstream, closing.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240527/1f3a84f7/attachment.sig>