Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Stephen Powell Subject: Re: Writing to the Windows Event Log Date: Fri, 20 Jun 2003 10:42:13 +1000 Organization: Hail Eris! Lines: 17 Message-ID: References: <21C1BC08EDD6F6489EC4C28E38E6AD2B0291F58F AT EMAIL DOT lgmt DOT trdo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (windows-nt) Hamster/2.0.1.3 Cancel-Lock: sha1:Gbzg1atcIEGR/UV6PuOd54NNaCU= On Thu, 19 Jun 2003, tsiegel AT intrado DOT com wrote: > I would like to be able to write to the Windows event application > log with my shell scripts running on Cygwin. Any "tried and true" > solutions would be appreciated. /bin/logger is part of inetutils. You use it like logger -p info -t "This is my Program" "This is my message" The -p parameter is info, warn or error and is written to the type field. The -t parameter is written into the source field of the event record. The message is written to the description field of the event record. -- Stephen Powell stephen_powell AT optusnet DOT com DOT au -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/