Date: Mon, 3 Oct 2022 16:22:22 -0400 From: Paul Procacci <pprocacci@gmail.com> To: Dan Mahoney <freebsd@gushi.org> Cc: questions@freebsd.org Subject: Re: Possible OS suggestion: make service status smarter about process runtime Message-ID: <CAFbbPuh4KzHLYEFOJh9d=fHuQAhaS-N-hwB0Bg8sUnf088UTnA@mail.gmail.com> In-Reply-To: <8E0D7E65-CA5D-4338-B4A4-0875B7E30B56@gushi.org> References: <8E0D7E65-CA5D-4338-B4A4-0875B7E30B56@gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000009d925205ea271a52
Content-Type: text/plain; charset="UTF-8"
On Mon, Oct 3, 2022 at 2:19 PM Dan Mahoney <freebsd@gushi.org> wrote:
> Hey all,
>
> There's no mailing list for "rc" commands so I'm putting this in generic
> questions.
>
> We've recently done some pkg upgrades and would like to restart the
> various services.
>
> It occurs to me that since the rc subsystem knows the command involved,
> (say, /usr/local/sbin/httpd), and already looks at the process table and
> the pid file to figure out if it's running, It's also possible to extend
> the output of service foo status to print how long a service has been
> running.
>
> Further, this could be extended such that there was a way of telling, post
> pkg upgrade or post freebsd-update install, which services were in need of
> a restart. (I.e. which files had mtimes newer than their runtimes).
>
> Thoughts on this? Is it worth a feature request?
>
>
>
>
To be frank, how long something's been running is not important, at least
in this context.
My only concern surrounding how long something has been running is simply
to ensure it's running successfully.
As for which services needing a restart, I personally don't see any benefit.
Either you're a sysadmin who's doing targeted updates, letting your users
know in advance a specific service is being restarted due to maintenance
anyways,
or you're a sysadmin who's not doing their due diligence in keeping track
properly of changes occuring on a given system and just taking whatever pkg
gives them.
I'm the former. That's to say when I run pkg to update packages it's
followed by restarting necessary services; all planned in advanced of which
my users are informed about it.
That's not to say I hate the idea however as some may find it useful. I am
not one of those people.
I just think something like this is best left for a separate application
that someone can obtain through the ports tree.
My 2 nickels.
Thanks,
Paul Procacci
--
__________________
:(){ :|:& };:
--0000000000009d925205ea271a52
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 3, 2022 at 2:19 PM Dan Ma=
honey <<a href=3D"mailto:freebsd@gushi.org">freebsd@gushi.org</a>> wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey all,<br=
>
<br>
There's no mailing list for "rc" commands so I'm putting =
this in generic questions.<br>
<br>
We've recently done some pkg upgrades and would like to restart the var=
ious services.<br>
<br>
It occurs to me that since the rc subsystem knows the command involved, (sa=
y, /usr/local/sbin/httpd), and already looks at the process table and the p=
id file to figure out if it's running, It's also possible to extend=
the output of service foo status to print how long a service has been runn=
ing.<br>
<br>
Further, this could be extended such that there was a way of telling, post =
pkg upgrade or post freebsd-update install, which services were in need of =
a restart.=C2=A0 (I.e. which files had mtimes newer than their runtimes).<b=
r>
<br>
Thoughts on this?=C2=A0 Is it worth a feature request?<br>
<br>
<br>
<br>
</blockquote></div><div><br></div><div>To be frank, how long something'=
s been running is not important, at least in this context.</div><div>My onl=
y concern surrounding how long something has been running is simply to ensu=
re it's running successfully.<br></div><div><br></div><div>As for which=
services needing a restart, I personally don't see any benefit.<br></d=
iv><div>Either you're a sysadmin who's doing targeted updates, lett=
ing your users know in advance a specific service is being restarted due to=
maintenance anyways,</div><div>or you're a sysadmin who's not doin=
g their due diligence in keeping track properly of changes occuring on a gi=
ven system and just taking whatever pkg gives them.<br><br></div><div>I'=
;m the former.=C2=A0 That's to say when I run pkg to update packages it=
's followed by restarting necessary services; all planned in advanced o=
f which my users are informed about it.<br></div><div><br></div><div>That&#=
39;s not to say I hate the idea however as some may find it useful.=C2=A0 I=
am not one of those people.<br></div><div>I just think something like this=
is best left for a separate application that someone can obtain through th=
e ports tree.<br></div><div><br></div><div>My 2 nickels.<br><br></div><div>=
Thanks,</div><div>Paul Procacci<br></div>-- <br><div dir=3D"ltr" class=3D"g=
mail_signature">__________________<br><br>:(){ :|:& };:</div></div>
--0000000000009d925205ea271a52--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPuh4KzHLYEFOJh9d=fHuQAhaS-N-hwB0Bg8sUnf088UTnA>