Are there any alternatives to syslogd? Currently we do not run any Linux servers, so it would be ideal if I could find a Windows solution so that I would not need to worry about an addition machine
3CDaemon utilities include a syslog server (along with FTP/TFTP servers etc).It is for Windows and it is free. 3CDaemon Utilities-Windows
Not sure if it matters, but we are using log4j.
I have tried SyslogAppender with 3CDaemon and it works. You can try it.
我绝对不建议将 Windows EventLog 作为应用程序日志的媒介。通常，您想要写入 EventLog 的是您通常写入 syslog 的“系统”内容 - 服务启动、服务死亡、驱动程序失败等。我不会将任何内部应用程序跟踪放入其中。
如果您在使用 logFaces 时遇到困难，请给我留言（我是它的作者）
There is some thin line between so called "system log" and "application log". I don't think syslog is a good idea for application logs, I think syslog fits better system related info (as the name goes), - the stuff around your own application which helps your application go - the infrastructure, drivers, services, daemons, guys like that. I could be wrong though.., not sure there are written rules about it, just using common sense.
I would definitely advise against windows EventLog as a medium for application logs. Usually what you want to write into EventLog is that "system" stuff you would normally write into syslog - service started, service died, driver failed, etc. I wouldn't place any internal application traces into there.
If you have difficulties with logFaces, please jot me a line (I'm its author)
发布评论
评论（3）
3CDaemon 实用程序包括系统日志服务器（以及 FTP/TFTP 服务器等）。它适用于 Windows，并且是免费的。
3CDaemon 实用程序-Windows
我已经尝试使用 SyslogAppender 和 3CDaemon，它可以工作。你可以尝试一下。
3CDaemon utilities include a syslog server (along with FTP/TFTP servers etc).It is for Windows and it is free.
3CDaemon Utilities-Windows
I have tried SyslogAppender with 3CDaemon and it works. You can try it.
所谓的“系统日志”和“应用程序日志”之间有一些细微的界限。我不认为 syslog 对于应用程序日志来说是一个好主意，我认为 syslog 更适合系统相关信息（顾名思义）， - 您自己的应用程序周围有助于您的应用程序运行的内容 - 基础设施、驱动程序、服务、守护进程，这样的人。但我可能是错的……不确定是否有书面规则，只是使用常识。
我绝对不建议将 Windows EventLog 作为应用程序日志的媒介。通常，您想要写入 EventLog 的是您通常写入 syslog 的“系统”内容 - 服务启动、服务死亡、驱动程序失败等。我不会将任何内部应用程序跟踪放入其中。
如果您在使用 logFaces 时遇到困难，请给我留言（我是它的作者）
There is some thin line between so called "system log" and "application log". I don't think syslog is a good idea for application logs, I think syslog fits better system related info (as the name goes), - the stuff around your own application which helps your application go - the infrastructure, drivers, services, daemons, guys like that. I could be wrong though.., not sure there are written rules about it, just using common sense.
I would definitely advise against windows EventLog as a medium for application logs. Usually what you want to write into EventLog is that "system" stuff you would normally write into syslog - service started, service died, driver failed, etc. I wouldn't place any internal application traces into there.
If you have difficulties with logFaces, please jot me a line (I'm its author)
如果您仅使用 Windows，请查看 Windows EventLog 比 syslog 更合适。
为此，Log4J 有 NTEventLogAppender
If you're Windows only, surly the Windows EventLog would be more appropriate than syslog.
Log4J has the NTEventLogAppender for this purpose