Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #239571

Re: masked service file

From Greg Wooledge <greg@wooledge.org>
Newsgroups linux.debian.user
Subject Re: masked service file
Date 2021-09-01 20:10 +0200
Message-ID <CSCQq-4wU-5@gated-at.bofh.it> (permalink)
References (5 earlier) <CSkgN-19w-1@gated-at.bofh.it> <CSzfP-2eP-1@gated-at.bofh.it> <CSAlA-2S3-9@gated-at.bofh.it> <CSAlA-2S3-7@gated-at.bofh.it> <CSCGJ-4ea-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Sep 01, 2021 at 01:52:21PM -0400, Dan Ritter wrote:
> Greg Wooledge wrote: 
> > On Wed, Sep 01, 2021 at 04:06:37PM +0100, mick crane wrote:
> > 
> > Do you think your init system has some way to know WHY it was given a
> > command?  And that it stores these reasons somewhere, and can cough them
> > up on demand?
> 
> Speaking as a professional sysadmin, I would welcome a required
> comment field on many system altering commands, so that a log
> could be kept and spit back on demand.
> 
> # service saned status
> saned is not running
> 20210704 14:02:33 user root stopped saned saying "interfering with new printer?"
> 
> Yeah, that would be nice.

I'd imagine that in practice, most people would put nothing, or "x", as
the reason, if they had to type a reason after every single command
they run as root.

That said, one of the data points you *can* get out of Debian for most
events is *when* they happened.  If mick crane wanted to ask *when*
the service was masked, and if they'd tell us the frickin' NAME of the
service they're asking about, we could probably tell them how to discover
when the service was masked.

In many cases, the timing can be a vital clue in one's explorations.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

masked service file mick crane <mick.crane@gmail.com> - 2021-08-31 19:40 +0200
  Re: masked service file john doe <johndoe65534@mail.com> - 2021-08-31 19:50 +0200
    Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-08-31 20:50 +0200
      Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-08-31 21:00 +0200
        Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-08-31 21:30 +0200
          Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-01 00:20 +0200
            Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-01 16:20 +0200
              Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-09-01 17:30 +0200
                Re: masked service file Dan Ritter <dsr@randomstring.org> - 2021-09-01 20:00 +0200
                Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-09-01 20:10 +0200
                Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-01 21:00 +0200
                Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-09-01 21:20 +0200
                Re: masked service file "Andrew M.A. Cater" <amacater@einval.com> - 2021-09-05 16:00 +0200
                Re: masked service file <tomas@tuxteam.de> - 2021-09-05 17:10 +0200
                Re: masked service file Curt <curty@free.fr> - 2021-09-08 18:10 +0200
                Re: masked service file <tomas@tuxteam.de> - 2021-09-08 18:10 +0200
                Re: masked service file Curt <curty@free.fr> - 2021-09-02 12:00 +0200
                Re: masked service file Greg Wooledge <greg@wooledge.org> - 2021-09-02 17:30 +0200
                Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-02 19:00 +0200
                Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-03 00:30 +0200
                Re: masked service file Brian <ad44@cityscape.co.uk> - 2021-09-03 01:30 +0200

csiph-web