Re: Great 022 mystery solved ... now how to fix

Hi -

> [...]
> The first snag I've run into with this approach is that any output from 
> these scripts goes to syslog rather than stdout and stderr, and our QA 
> *.out files are riddled with lines like:
> 
> Waiting for pmcd to terminate ...
> Starting pmcd ...
> Starting pmlogger ...
> 
> and these are no longer present.  Dredging with journalctl is not 
> looking particularly attractive, so I'm back in thinking about it mode.

How about teaching the systemd .service files to launch pmcd in a more
proper native mode (not by naive delegation to the displaced
initscripts files)?  Then those dispaced files can learn to delegate
to systemd for startup, rather than launching pmcd directly.  But they
can print the same message as before.  (Those messages could be fake,
or perhaps even pulled out of the journal.)  So if the qa scripts use
the initscripts, they would see the same messages and have same
control.

- FChE

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#15045): https://groups.io/g/pcp/message/15045
View All Messages In Topic (4): https://groups.io/g/pcp/topic/4255730
Mute This Topic: https://groups.io/mt/4255730?uid=174580
New Topic: https://groups.io/g/pcp/post
-=-=-
pcp mailing list
[email protected]
https://groups.io/g/pcp/messages
-=-=-
Change Your Subscription: https://groups.io/g/pcp/editsub?uid=174580
Group Home: https://groups.io/g/pcp
Contact Group Owner: [email protected]
Terms of Service: https://groups.io/static/tos
Unsubscribe: https://groups.io/g/pcp/leave/354243/563757577/xyzzy
-=-=-=-=-=-=-=-=-=-=-=-