BOINC Messages now going to syslog

Message boards : Questions and problems : BOINC Messages now going to syslog
Message board moderation

To post messages, you must log in.

AuthorMessage
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 86325 - Posted: 26 May 2018, 19:41:54 UTC - in response to Message 86323.  

The logs is now managed by systemd's journald. You can read them with journalctl -u boinc-client or your favourite GUI log reader.

If you must have the log in a file Stack Overflow tells you how.
ID: 86325 · Report as offensive
Gary Roberts

Send message
Joined: 7 Sep 05
Posts: 130
Australia
Message 86380 - Posted: 30 May 2018, 6:59:09 UTC - in response to Message 86325.  
Last modified: 30 May 2018, 7:15:16 UTC

The logs is now managed by systemd's journald.

What happens for distros that don't use systemd?

My distro of choice refuses to go down the systemd route and even refuses to package BOINC. That doesn't bother me as I've always just unpacked the shell archive and used the contents. I've built 7.6.33 and 7.9.3 myself so I do know how to get the source and build it. I'm just a little concerned as to what might happen in future if, perhaps, BOINC now depends on systemd, or is changing in other ways that might affect me.

I built 7.9.3 about a month ago but before I had even started testing what I had built, the 7.10.x series came along. I decided to wait for any initial glitches to be ironed out and then build and test a new 7.10.x, rather than waste time with 7.9.3. All builds I've done have produced a shell archive, as well as the individual executables, which suited me just fine. It's what I've used since the year dot for the way I deploy over a fleet of hosts. From a bit of what I've been reading lately, I'm wondering if my preferred way of doing things might have to change. Please tell me my fears are groundless :-).

EDIT: Just as a small example of my concerns, I have quite a few shell scripts that interrogate stdoutdae.txt, as well as other things. I don't particularly relish the prospect of rejigging a lot of stuff because of changes to logs, etc, that had a standard location and format for many years.
Cheers,
Gary.
ID: 86380 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 86499 - Posted: 8 Jun 2018, 20:55:10 UTC - in response to Message 86380.  

Nothing to worry about. This is just Debian/Ubuntu/... package change.

The client continues to log into stdoutdae.txt and stderrdae.txt if --redirectio is specified on the command line. Otherwise it outputs to stdout and stderr and you are free to redirect the output where you want.

In Debian package client is now told to do the latter and systemd just grabs the output and puts it into journal.
ID: 86499 · Report as offensive
Gary Roberts

Send message
Joined: 7 Sep 05
Posts: 130
Australia
Message 86501 - Posted: 9 Jun 2018, 4:27:30 UTC - in response to Message 86499.  

OK, fine. Thanks very much for the response.
Cheers,
Gary.
ID: 86501 · Report as offensive

Message boards : Questions and problems : BOINC Messages now going to syslog

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.