-----Original Message----- From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-bounces at lists.wpkg.org] On Behalf Of Falko Trojahn Sent: 08 July 2008 13:03 To: Rainer Meier Cc: wpkg Subject: Re: [wpkg-users] WPKG Client 1.3.4 released (testing release), including 64 bit support Yes, this is clear. It's just an idea for convenience: if I restart the wpkg service on local or remote pc from Wpkginst tool I don't have to open event log viewer, connect to the Client, open "events", open "application" and have a look through the messages. Easily I could have a look at the messages in wpkg tool. Perhaps a button / link to open the application event log of the pc there I (re)started wpkg would be ok, too. Opening the event log of the pc and filter for "WSH" is perhaps easier to integrate in wpkginst than opening the log file for the client, isn't it? [Leon Hedding] I sort this issue by using centralized logging that I can run tail -f upon. I do this by modifying wpkg.js to not overwrite the log file and by adding log rotation to wpkg.js. The reason I don't use logrotate is because WPKG might not be installed on a Windows box which does not have this installed and because I could not be bothered trying to figure out how logrotate would work with my logging scheme. [Leon Hedding] |