[wpkg-users] cmd /c hanging?

[Tomasz Chmielewski]

> I have a couple of packages that are using cmd /c <command> to install and
> remove software and sometimes the cmd window seems to hang and I have to
> kill it.  The cmd runs fine if I cut and paste it into a cmd prompt on the
> machine.  Any ideas what would cause such on issue?
>
> Here's one package that's giving me the problem.  The 2nd command copies 2
> files and the 3rd copies 45 files.  It's the 3rd command that it tends to
> hang on.  When I run this manually it takes less than 2 seconds to copy the
> 45 files.

Yes, probably you run WPKG with /quiet flag.
This means it logs all what WPKG says to Windows event log.

By default, Windows event log is 512 + 128 + 64 kB large, for various event groups (rotated).
Isn't it a joke? 720 kB maximum logs? So that they could fit on a single side floppy, anyone still remember those? :)

You use "copy" command, and I believe your "copy" is running in verbose mode, so it produces a lot of text, which gets appended to the event log.

So you have at least three solutions:

1) increase the size of event log on all your Windows workstations

2) don't use /quiet with wpkg.js

3) run "copy" (and all other commands that produce output) in a quiet/silent mode.
If the quiet/silent mode is not available, you can make the command quiet by appending >nil at the very end of the command.


So, point 3 is the easiest and recommended.


-- 
Tomasz Chmielewski
http://wpkg.org








_______________________________________________
wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users