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?
nelgin wrote to All <=-
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. :-)
I hated systemd to start with, however having used it for a while
now, I have found it's extremely powerful.
For example:
I am now running each part of sbbs separately, term, services,
mail, webserver and ftp. Each has their own startup script such
as
sbbs-ftp.service, sbbs-term.service and they are controlled as a
group by sbbs.service
So I can start and stop each individually or as a group.
I do a similar thing with sexpots. I have 4 lines and each one
runs via an independent systemd file, but can be controlled as a
group.
It's easy to run sbbs as a separate user, and set parameters for
the environment that it'll run in.
Yes, Slackware does not, and likely never will, use systemd. That's a
Good Thing in my opinion. :-)
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.
Yep, I have a Debian box and some other variants and have noticed that
too. I don't know much about it, but the "journalctl" command may help.
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).
That's probably an option; don't think it would hurt anything to have two logs, if it allows you to use the tools you prefer. Good luck.
The console. And the traditional BBS sessions are logged to files in the data/
gs directory.
My sbbs.ini has:
; Defaults to using the USER facility.
LogFacility = 1
; syslog identity to use (when daemonized)
LogIdent = synchronet
And then to see synchronet logs, I use:
journalctl -f --since "today" -tsynchronet
I dont recall if I did anything on the systemd side (dont remember), and haven
figured out how to use journalctl with any anger - but the command above gets
what I need...
The console. And the traditional BBS sessions are logged to files in the data/
gs directory.
So it only goes to the console?
I have seen those logs, they don't hold much info when it comes to non-traditional sessions, like a QWK node uploading REP packets.
Are you running synchronet daemonized? I am not, and the sbbs.ini notes seem to indicate that this only works when you are, but will try those settings and see if I am reading that wrong. Thanks.
I have seen those logs, they don't hold much info when it comes to non-traditional sessions, like a QWK node uploading REP packets.
That's right.
Re: Syslog and Windows
By: dragon to Digital Man on Fri Feb 16 2024 07:47 pm
> 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?
If you run Synchronet on Windows a NT services, then all the log output goes to the Synchronet Event log:
https://wiki.synchro.net/monitor:ntsvcs
I don't have experience with it, but apparently using something like EventReporter, you can forward all Windows event log messages to a syslog server.
On 2/16/2024 21:12, Digital Man wrote:
Re: Syslog and Windows
By: dragon to Digital Man on Fri Feb 16 2024 07:47 pm
> 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?
If you run Synchronet on Windows a NT services, then all the log output goes to the Synchronet Event log:
https://wiki.synchro.net/monitor:ntsvcs
I don't have experience with it, but apparently using something like EventReporter, you can forward all Windows event log messages to a syslog server.
Quite a lot of functionality is lost by running Synchronet as a service.
I would much prefer to have Synchronet send log entries directly to a remote syslog server. If this seems too difficult to implement, I won't keep pushing the idea.
I would much prefer to have Synchronet send log entries directly to a remote syslog server. If this seems too difficult to implement, I won't keep pushing the idea.
Nobody's ever made the request before. <shrug>
Quite a lot of functionality is lost by running Synchronet as a service.
I would much prefer to have Synchronet send log entries directly to a remote syslog server. If this seems too difficult to implement, I won't
keep pushing the idea.
Quite a lot of functionality is lost by running Synchronet as a service.
I would much prefer to have Synchronet send log entries directly to a
remote syslog server. If this seems too difficult to implement, I won't
keep pushing the idea.
Since it sounds like you are talking about windows, this may not be an option, but I think that rsyslog gives you the option to send the output to
a remote syslog server. That should mean that individual software programs don't need to know how to do it on their own.
* SLMR 2.1a * Avoid reality at all costs.
---
� Synchronet � CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
On 2/20/2024 08:52, Dumas Walker wrote:
Quite a lot of functionality is lost by running Synchronet as a service. >> I would much prefer to have Synchronet send log entries directly to a >> remote syslog server. If this seems too difficult to implement, I won't >> keep pushing the idea.
Since it sounds like you are talking about windows, this may not be an option, but I think that rsyslog gives you the option to send the output to
a remote syslog server. That should mean that individual software programs don't need to know how to do it on their own.
* SLMR 2.1a * Avoid reality at all costs.
---
¨ Synchronet ¨ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
I am talking Windows.
I manage multiple mail, s/ftp, im, firewall, and other servers spread
out all over the World on a variety of OSes. Most of these are able to
send messages to a central syslog server.
There's also an IDS system sending syslog alerts.
Currently, Synchronet's logs are bundled up by some scripts that forward them to syslog. I would like to remove the delay this introduces to
that to, for instance, update my firewall against hack attempts.
Re: Re: Syslog and Windows
By: dragon to Dumas Walker on Sun Feb 25 2024 10:49 pm
> On 2/20/2024 08:52, Dumas Walker wrote:
> >> Quite a lot of functionality is lost by running Synchronet as a service.
> >> I would much prefer to have Synchronet send log entries directly to a
> >> remote syslog server. If this seems too difficult to implement, I won't
> >> keep pushing the idea.
>
> > Since it sounds like you are talking about windows, this may not be an
> > option, but I think that rsyslog gives you the option to send the output
> > to
> > a remote syslog server. That should mean that individual software
> > programs don't need to know how to do it on their own.
>
>
> > * SLMR 2.1a * Avoid reality at all costs.
>
> > ---
> > � Synchronet � CAPCITY2 * capcity2.synchro.net *
> > Telnet/SSH:2022/Rlogin/HTTP
>
> I am talking Windows.
>
> I manage multiple mail, s/ftp, im, firewall, and other servers spread
> out all over the World on a variety of OSes. Most of these are able to
> send messages to a central syslog server.
>
> There's also an IDS system sending syslog alerts.
>
> Currently, Synchronet's logs are bundled up by some scripts that forward
> them to syslog. I would like to remove the delay this introduces to
> that to, for instance, update my firewall against hack attempts.
Are you using a Syslog Agent for Windows?
Do your other Windows applications have built-in syslog support? Are they open source?
If you know, what format syslog msgs are you/they using: BSD or IETF format?
| Sysop: | Manitoo |
|---|---|
| Location: | Montreal, QC, Canada |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 104:26:35 |
| Calls: | 37 |
| Files: | 3 |
| Messages: | 30,290 |