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.

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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?

#

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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?

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!




... HAL 9000 - Dave. Put down those Windows disks. Please, Dave.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Moving SBBS logging out of syslog
By: Dumas Walker to All on Fri Feb 16 2024 10:26 am

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?

It goes to syslog (the daemon/service, not necessarily the file "syslog"). Look at your syslog configuration file to find out which *files* it goes to. Or use something like journalctl (if you have it) to view them based on service. There's also tools like lnav which are nice for viewing logs.
--
digital man (rob)

Synchronet/BBS Terminology Definition #77:
SSL = Secure Sockets Layer (precursor to TLS)
Norco, CA WX: 58.9øF, 75.0% humidity, 3 mph SSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On Fri, 16 Feb 2024 08:58:27 -0500
"Dumas Walker" (VERT/CAPCITY2)
<VERT/CAPCITY2!Dumas.Walker@endofthelinebbs.com> wrote:

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.

#

---
â–  Synchronet â–  CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

FWIW
$ cat /etc/rsyslog.d/40-synchronet.conf
if $programname == 'synchronet' then {
if $msg startswith ' web ' then {
action(type="omfile" file="/var/log/sbbs/web.sbbs.log"
fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' mail '
then { action(type="omfile" file="/var/log/sbbs/mail.sbbs.log"
fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' srvc '
then { action(type="omfile" file="/var/log/sbbs/service.sbbs.log" fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' evnt BINK'
then { action(type="omfile" file="/var/log/sbbs/binkit.sbbs.log" fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' evnt '
then { action(type="omfile" file="/var/log/sbbs/event.sbbs.log"
fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' term '
then { action(type="omfile" file="/var/log/sbbs/term.sbbs.log"
fileOwner="bbs" fileGroup="bbs") } else if $msg startswith ' ftp ' then
{ action(type="omfile" file="/var/log/sbbs/ftp.sbbs.log"
fileOwner="bbs" fileGroup="bbs") }
else
{
action(type="omfile" file="/var/log/sbbs/sbbs.log" fileOwner="bbs" fileGroup="bbs") }
stop
}
if $programname == 'ircd' then {
action(type="omfile" file="/var/log/sbbs/ircd.log" fileOwner="bbs" fileGroup="bbs") stop
}
I basically get a different file for each service in /var/log/sbbs
in my systemd file
#StandardOutput=syslog
#StandardError=syslog
SyslogIdentifier=synchronet
#SyslogFacility=local3
All the logging stuff is commented out except for SyslogIdentifier.
sbbs.ini contains
; Defaults to using the USER facility.
LogFacility=3
; syslog identity to use (when daemonized)
LogIdent=synchronet
Somehow, it all works.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
---
ï¿­ Synchronet ï¿­ End Of The Line BBS - endofthelinebbs.com

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?

---
þ Synchronet þ IPTIA - bbs2.ipingthereforeiam.com:2323

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.
--
digital man (rob)

Breaking Bad quote #15:
Cheer up Gomey, your people still got J. Lo. - Hank Schrader
Norco, CA WX: 58.6øF, 78.0% humidity, 2 mph W wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

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.

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."

To my knowledge, there is no syslog configuration file because rsyslog is
not installed -- it was replaced with the stupid systemd journaling crap
which, as I have figured out, doesn't work so good. I actually just
checked. /etc/rsyslog.d is still there, but its contents are being ignored
by the broken new replacement.

It is like a linux dev decided to answer a question that no one asked --
how can I make it harder for users who are good with cat, grep, head, tail, etc., to check their logs? -- and the predictably dumb answer was journalctl.

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? It currently looks like nowhere, so I'd like to fix that if possible.

If not possible, I will check into reinstalling rsyslog and living with everything (supposedly) being logged twice, which seems like a real PITA.


* SLMR 2.1a * "For there is no sea, with out the dolphin" -- Oppian

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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).


* SLMR 2.1a * I was a tall person before I used PKZIP...!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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.

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.

# 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).

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.


... All the easy problems have been solved.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: Moving SBBS logging o
By: Dumas Walker to DIGITAL MAN on Sat Feb 17 2024 10:48 am

Howdy,

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."

FWIW, I'm using journalctrl.

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 havent figured out how to use journalctl with any anger - but the command above gets me what I need...


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

On Sat, 17 Feb 2024 15:00:00 -0600
"Gamgee" (VERT/PALANTIR) <VERT/PALANTIR!Gamgee@endofthelinebbs.com>
wrote:

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.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Re: Moving SBBS logging o
By: Dumas Walker to DIGITAL MAN on Sat Feb 17 2024 10:48 am

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?

The console. And the traditional BBS sessions are logged to files in the data/logs directory.
--
digital man (rob)

Synchronet "Real Fact" #7:
The name "Synchronet" was suggested by Steve Deppe (Ille Homine Albe) in 1991 Norco, CA WX: 53.5øF, 82.0% humidity, 7 mph W wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

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.

While it "may" make some things more convenient, any of that stuff can
be done the "old fashioned way" with scripts, probably in /etc/rc.d ,
and passing of command-line parameters (like start|stop|restart).



... She kept saying I didn't listen to her, or something like that.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Yes, Slackware does not, and likely never will, use systemd. That's a
Good Thing in my opinion. :-)

Indeed. I run devuan on a couple of boxes for that reason, but I have
found it is not real reliable for my use if I need X windows. So it runs
on cli only machines and in a couple of VMs.

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.

It might except...

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.

It is not so much that, but journalctl is supposed to be able to show me
the syslog logging if I give it a '-u syslog' but it reports there are no entries. Oooops! ;)


* SLMR 2.1a * <A>bort <R>etry <S>hoot the SOB!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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.


* SLMR 2.1a * We're having an adventure, just like the Goonies!!!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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...

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.


* SLMR 2.1a * Camel: A quarter horse designed by a committee.

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: Moving SBBS logging o
By: Dumas Walker to DIGITAL MAN on Sun Feb 18 2024 11:00 am

The console. And the traditional BBS sessions are logged to files in the data/
gs directory.

So it only goes to the console?

Correct.

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.
--
digital man (rob)

Synchronet/BBS Terminology Definition #6:
BBS = Bulletin Board System
Norco, CA WX: 63.8øF, 61.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Moving SBBS logging o
By: Dumas Walker to DEON on Sun Feb 18 2024 10:40 am

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 am.

I start my SSBS with "sbbs -d" from a script.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI

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.

I installed rsyslog and all is well again.


* SLMR 2.1a * I still miss my Ex... But my aim _is_ improving!

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

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.

---
þ Synchronet þ IPTIA - bbs2.ipingthereforeiam.com:2323

Re: Re: Syslog and Windows
By: dragon to Digital Man on Mon Feb 19 2024 08:03 pm

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.

What functionality is that? With the addition of MQTT support in v3.20, I plan to make running Synchronet as an NT service to as natural (and featureful) as it is to run it as a daemon on *nix.

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>
--
digital man (rob)

Breaking Bad quote #13:
I got twenty bucks that says he's a beaner. - Hank Schrader
Norco, CA WX: 53.0øF, 96.0% humidity, 0 mph NW wind, 0.10 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: Syslog and Windows
By: Digital Man to dragon on Mon Feb 19 2024 10:05 pm

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>

Hey, guy who runs serveral external servers here.

i don't think it's necessary to be implimented directly into synchronet.
they can have this functionality via scripting or editing the source code.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::

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.

---
þ Synchronet þ IPTIA - bbs2.ipingthereforeiam.com:2323

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?
--
digital man (rob)

Breaking Bad quote #23:
Whiteboy's gonna kick your ass if you don't stop wasting his time. - Hank Norco, CA WX: 60.9øF, 73.0% humidity, 3 mph SSE wind, 0.01 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 2/26/2024 16:15, Digital Man wrote:

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?

Currently I'm using a syslog server my buddy and I wrote in Perl. I've
used free and commercial Syslog servers for Windows as well. None of
those were open source, which is what prompted creating our own.

I have several closed souced commercial Windows applications, as well as numerous Perl applicationes we wrote sending to syslog.

The Perl syslog server is format agnostic and can deal with IETF or BSD format. I actually run 2 instances, one for each. Only one application currently uses BSD format.

If you're looking for example code for sending messages, the Perl
Net::Syslog module has it all and is pretty small.

---
þ Synchronet þ IPTIA - bbs2.ipingthereforeiam.com:2323