Please reply using this URL only: http://bugs.wpkg.org/show_bug.cgi?id=33
------- Additional Comments From [EMAIL PROTECTED] 2006-12-05 15:33 ------- (In reply to comment #9) > the difference is the outputformat. this way you have more control over how > the > output is saved in the log file. > and this is not only intended for debug purpuses, but also for documentation > that installation was ok. It also gives the opportunity to see the success/failure of an install even when the computer is not turned on since the logging is in one central place and not in the eventvwr of all the computers on the network. I realized that I could just remove the /quiet parameter but I need to have the dates/times for each thing being logged. Piping the command line does not do this. It would be really nice to have a parameter that I can say wpkg.js /log:<directory>\computername_01.log and it logs to that location with the date and time of each command performed by wpkg. It also needs log rotation after the file gets to a certain size. The log rotation might be best in the wpkg installer. -- Configure bugmail: http://bugs.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wpkg-users mailing list wpkg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wpkg-users
