Re: logging no longer standard?
On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:
> On 8/7/23 13:23, Henning Follmann wrote:
> > On Mon, Aug 07, 2023 at 09:41:11AM -0400, gene heskett wrote:
> > > On 8/7/23 07:50, Henning Follmann wrote:
> > > > On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
> > > > > On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> > > > > > On Sat, 5 Aug 2023 15:09:41 +0000
> > > > > > Andy Smith <andy@strugglers.net> wrote:
> > > > >
> > > > [...]
> > > > > In some cases, the release notes actually do tell you how to get back
> > > > > to normal.
> > > > err,
> > > > "how to get back."
> > > > Normal is the new systemd
> > > >
> > [deleted rant novella]
> >
> > Breathe!
> >
> > Your issues are not solved by or caused by either of journald or rsyslog.
> > These are just writing what is given to them to somewhere.
> > If it is not in the log it's someone else's fault.
> >
> > -H
> Ohhhkaaay, but why then do I get a message if looking at the journal as user
> 1000, that the user must be a member of the adm group to see all the log,
> AND adding me to the adm group doesn't change what I can see using sudo? I
> see gigabytes of stuff from kwin etc, but nary a syllable from what isn't
> working because something blocks it.
>
> Cheers, Gene Heskett.
I have no idea what is going on on your system. The history of this
mailing list is littered with threads where you do things the "Gene" way and
shooting yourself in the foot. I just assume it's another one.
I am out of this subthread.
-H
--
Henning Follmann | hfollmann@itcfollmann.com
Reply to: