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: | smooth0401 |
|---|---|
| Location: | New Providence, NJ |
| Users: | 3 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 474:40:53 |
| Calls: | 351 |
| Files: | 725 |
| D/L today: |
8 files (11,151K bytes) |
| Messages: | 57,667 |