Several years ago I set my BBS up to write the log to syslog. Recently, some shit for brains decided that having syslog was "bad" so now there is no easy way to just load syslog and search it.
I want to revert back to having Synchronet keeps its own log. How do I do that?
And, no I am not looking for a lecture on how this way is better.
Thanks.
Dumas Walker wrote to All <=-
Several years ago I set my BBS up to write the log to syslog.
Recently, some shit for brains decided that having syslog was
"bad" so now there is no easy way to just load syslog and search
it.
I want to revert back to having Synchronet keeps its own log.
How do I do that?
Several years ago I set my BBS up to write the log to syslog. Recently, some shit for brains decided that having syslog was "bad" so now there is no easy way to just load syslog and search it.
I want to revert back to having Synchronet keeps its own log. How do I do that?
And, no I am not looking for a lecture on how this way is better.
Thanks.
Nevermind, I found the answer right after posting. Now, if I take 'syslog' off the command line, and I am not running daemonized, where does the log go? The wiki mentions sbbs.log, but I am not finding that in /var/log or ~/data/logs. Where does it go?
Several years ago I set my BBS up to write the log to syslog.FWIW
Recently, some shit for brains decided that having syslog was "bad"
so now there is no easy way to just load syslog and search it.
I want to revert back to having Synchronet keeps its own log. How do
I do that?
And, no I am not looking for a lecture on how this way is better.
Thanks.
#
---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net *
Telnet/SSH:2022/Rlogin/HTTP
I'm running Synchronet on Windows. I have most of my other services on dozens of machines sending log data to a central Windows syslog server.
I would LOVE to get Synchronet to do that as well. Possible?
It goes to syslog (the daemon/service, not necessarily the file "syslog"). Loo
at your syslog configuration file to find out which *files* it goes to. Or use
omething like journalctl (if you have it) to view them based on service. There
also tools like lnav which are nice for viewing logs.
Several years ago I set my BBS up to write the log to syslog.
Recently, some shit for brains decided that having syslog was
"bad" so now there is no easy way to just load syslog and search
it.
I want to revert back to having Synchronet keeps its own log.
How do I do that?
I am using Slackware Linux, and in my /etc/syslog.conf I've added this
near the bottom of the file:
# Synchronet BBS logging - added by Dan C. 2/17/19
local3.* -/var/log/sbbs.log
The "3" on the end of the "local" keyword is because I've also changed
my /sbbs/ctrl/sbbs.ini to have this in the [UNIX] section at the bottom:
; Defaults to using the USER facility.
LogFacility = 3
The result of these two settings produces my log in /var/log/sbbs.log
Hope that helps!
Dumas Walker wrote to DAN CLOUGH <=-
Several years ago I set my BBS up to write the log to syslog.
Recently, some shit for brains decided that having syslog was
"bad" so now there is no easy way to just load syslog and search
it.
I want to revert back to having Synchronet keeps its own log.
How do I do that?
I am using Slackware Linux, and in my /etc/syslog.conf I've added this
near the bottom of the file:
Sounds like maybe Slackware Linux, or at least the version you
are running, has not switched over to systemd? That happened a
few debian versions ago.
With the latest version, they've replaced rsyslog with some
systemd journaling. I can learn some new tool(s) to get to the
syslog output I want, *IF* they worked as documented which they
do not here.
# Synchronet BBS logging - added by Dan C. 2/17/19
local3.* -/var/log/sbbs.log
The "3" on the end of the "local" keyword is because I've also changed
my /sbbs/ctrl/sbbs.ini to have this in the [UNIX] section at the bottom:
; Defaults to using the USER facility.
LogFacility = 3
The result of these two settings produces my log in /var/log/sbbs.log
Hope that helps!
I may have to reinstall rsyslog and live with the syslog output
being both written to file and (maybe) journaled (although it
does not really appear to be like it is supposed to be).
I looked into journalctl. It is supposed to show syslog output with the option '-u syslog' but it does not. It claims there are "no entries." It does not know what 'sbbs' is, presumably because I don't run it daemonized, so there are also "no entries."
Sounds like maybe Slackware Linux, or at least the version you
are running, has not switched over to systemd? That happened a
few debian versions ago.
Yes, Slackware does not, and likely never will, use systemd. That's
a Good Thing in my opinion. :-)
So I don't want synchronet logging going to "syslog" anymore, file or otherwise. Now that I have taken syslog off the command line, where is sbbs logging to?
Sysop: | neur0mancer |
---|---|
Location: | Colorado Springs, CO |
Users: | 21 |
Nodes: | 10 (0 / 10) |
Uptime: | 193:03:20 |
Calls: | 269 |
Messages: | 53,234 |