> On Tuesday, July 25, 2023 at 12:50:53 PM PDT, Tom Longfellow
> <03e29b607131-dmarc-requ...@listserv.ua.edu> wrote:
> If I was talking Linux I would look around.
z/OS Unix can use any open source syslog processor. SYSLOGD is distributed with
most flavors Unix and Linux. I'm just saying
If I was talking Linux I would look around.
I am a tried and true z/OS user and SYSLOGD is all I know.
I have my complaints about it. It only supports UDP protocol - and IBM tape
and disk hardware only talk TCP protocol to report errors.
But I pick my battles in live with what I am given
About cut and past in that message.The TRMD line has been working fine for
some time now.
The path name changes as a result of a cron command to 'kill -HUP the pid'
Restart happens and new files open.
I can see the advantage of a name change if I was actively using the data. It
is
> On Tuesday, July 25, 2023 at 07:03:40 AM PDT, Tom Longfellow wrote:
> It turns out that the core of my problem was my interpretation of a few
> 'quirks' in syslog defining.
SYSLOGD does not solve every syslog problem thus you will find over a dozen
alternatives. I'm not recommending what to
The syslog.conf rules that you say that you use on your website don't seem to
match your active files.
For example, it looks like you have a rule:
.TRMD**.***.*** /var/log/%Y/%m/%d/trmd*
I'm not certain, but by my reading of the Comm Server IP Configuration Guide
this will be a problem:
I think I am on the right track now.
On a personal note, I have always had difficulty working with 'Reverse' logic,
like my Reverse Polish Notation (RPN) calculator in my ancient College past.
I had tried the use of the '!' in the directives to no advantage several times
over the years.
It
On 7/24/23 1:42 PM, Tom Longfellow wrote:
I am sure that all of Unix Gurus will laugh at my ignorance, but I still
cannot break through this wall.
A /good/ Unix Guru worth their disk space will NOT laugh at you / your
perceived ignorance. A BOFH will laugh at most things, even legitimate
No sweat, Tom. And no laughing.
Not sure how to *exclude* things, but I use two catchall statements.
(And I avoid fancy extensions to the original specification: keep it
simple.)
So my /etc/syslog.conf looks mostly like ...
*.info /var/log/messages
*.info @loghost
The first
I apologize to all who have seen this before. BUT since I cannot find my
original post here, I am going to try again.
I am sure that all of Unix Gurus will laugh at my ignorance, but I still cannot
break through this wall. The syntax of syslogd.conf is a complete mystery of
arcane
