http://bugzilla.wpkg.org/show_bug.cgi?id=158 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.meier at wpkg.org --- Comment #1 from Rainer Meier <r.meier at wpkg.org> 2009-05-06 16:33:02 --- Looks like a simple "tail" program for Windows. However I think your request cannot be processed as you suggested. First of all when running a service the service cannot display any window - no interaction with the user desktop is allowed by services running with SYSTEM privileges on Windows Server 2003 and newer. On Windows XP it was possible to enable the "Allow service to interact with desktop" checkbox to allow this but in Windows Server 2003 and newer (including Vista, Windows Server 2008*, Windows 7) it is not allowed any more. As far as I know it would be allowed for "normal" administrator accounts. But this would require to create an independent local service account for WPKG and run the WPKG service with this credentials. Moreover such a pop-up window would appear on _every_ service run (i.e. on Windows startup too). I think a window showing the current progress is mainly interesting for system administrators. And here there is already a solution. Just use cygwin tail (or TailXP if you prefer) on the log file written by WPKG. Administrators using unix/Linux servers might use the tail program which is included in every Linux distribution. This perfectly allows you to follow the execution of the script. Moreover it's possible this way to define the level of output independently from the system event log verbosity. By default WPKG only prints informational, warning and error messages to the event log to prevent polluting it. Also remember that using the /debug command-line switch prints all debug messages to event log which could easily fill up the whole event log space in one run and then Windows or some programs might start to behave oddly (once we had a bug-report about this). So I suggest using what is already available. Use any tail program on the log file and then follow the output. I just noticed that TailXP can also follow the event log entries and display them as they are written to the log. Again, I still think this is more an administrator task and therefore simply running tailxp before running the wpkg service would be enough. Let's see what Tomasz thinks about - probably he has some more input. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |