Introduction[]
This article goes over the methods to handle cygwin application output.
Using syslogd[]
By default, if syslogd is not installed, your Windows event viewer will be riddled with events from your cygwin binaries like so:
The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found.
Sources
http://ronrothman.com/public/leftbraned/cygwin-cron-spurious-messages-in-event-viewer/
http://cygwin.com/ml/cygwin/2004-07/msg00385.html
http://www.cygwin.com/ml/cygwin/2004-11/msg00134.html
Using log files[]
Be sure to make your log file accessible to the user:
- Change to ownership of the files required by the sshd service owner. Open a cygwin bash session and run these commands for your userid [http://www.cygwin.com/ml/cygwin/2004-11/msg00134.html $ chown userid /var/log/sshd.log
$ chown -R userid /var/empty $ chown userid /etc/ssh* ]
[http://www.cygwin.com/ml/cygwin/2004-11/msg00134.html Where the userid is...
]