[Novalug] [Opinion] The age of "Guilt-By-Knowledge" and how the anti-system crowd has "won"

James Ewing Cottrell III JECottrell3@Comcast.NET
Sun May 3 01:37:52 EDT 2015


So you drew a different meaning from what Greg said, which was 
admittedly vague.

And I will concede that you get more, maybe even too much, info from 
systemd status. But you get less from ps than from service status.

FYI, I worked CentOS 7 into our Kickstart and SmartCard environment and 
used it for a few months in early summer of 2014. I disabled, enabled, 
stopped, and started many a daemon. I know a few basic tricks.

So please don't assume I have NO knowledge of have made NO Attempt to 
Acquire any.

JIM

On 5/3/2015 12:51 AM, Bryan J Smith wrote:
> On Sun, May 3, 2015 at 12:41 AM, James Ewing Cottrell III
> <JECottrell3@comcast.net> wrote:
>> Just to be clear, it was Greg who was saying that he never used the status
>> commands, that he used ps and grep.
>
> Yes, although I made a Freudian slip and called him "Grep" in one response.  ;)
>
>> I believe this is wrong, that one should use the "service whatever status"
>> command...at least initially. PS should be reserved when Service gets
>> confused.
>> What I thought was Funny was him saying how "systemctl status whatever" was
>> better than "service whatever status".
>> But I may have misinterpreted Greg's comments....perhaps he was referring to
>> the subservices...the ones that xinetd had started.
>
> Jim, I should have long taking this off-list.
>
> Because I'm purposely taking advantage of your unfamiliarity (which I
> polarized as "ignorance") with systemd, your resulting backtracking on
> this (despite my even posting several examples of "status" output from
> systemd), and it's wholly unfair to do this to you.  You obviously
> have a lot of years of experience with UNIX, and I'm now taking you on
> a guided tour of how to poorly fudge knowledge of systemd.  ;)
>
> So, 100% transparency, wanting to be 100% helpful here, humor me.
>
> 1.  SSH into any RHEL7/CentOS7 system you know of
> 2.  Run "service sshd status" (which gets redirected as "systemctl
> status sshd.service")
>
> Now understand what Greg, and I in the several follows-ups, meant.
> You will _not_ be running various "other commands" any more.  ;)
>
> -- bjs
>




More information about the Novalug mailing list