[wpkg-users] [Bug 169] Network info in logfile

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=169


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-08-05 18:36:35 ---
Personally I have some strong doubts that this will be as easy as you expect it
to be. There seems to be no portable way of accessing all the information you
ask for.
On Windows ipconfig /all pretty much prints all you listed there. However due
to some terrible bugs in WSH which will never be fixed by Microsoft it's not
possible to redirect its output in a reliable way.

In addition I remember lots of discussions on the mailing list where the
(rarely called code) of WPKG to detect the IP address randomly fails on various
systems.

Introducing a source of possible exceptions during each single WPKG run for the
sake of collecting information which is usually not needed looks like a very
bad approach to me.

If you're able to write a perfectly portable code for Win 9x, 2k, XP, Vista and
Windows 7 which reliably fetches all this information please contribute some
code sniplets and provide support for this part. From my side I currently
clearly vote not to implement such code because from my point of view it's not
even a source for possible errors but will for sure introduce problems.

Instead you could use WPKG pre-/post-execution or wrap WPKG within a simple
script which just prints the machine configuration to a file.

@echo off
ipconfig /all >> \\x.x.x.x\share\logfile.txt
exit  0


Note that in your case even resolving the host might fail and/or WPKG-client
might fail to invoke the remotely stored wpkg.js.

Actually I even doubt that this would be much more helpful. Usually I would
assume that network settings are correct and if an error like you describe
happens I would do all the steps manually and already at the second step
(connecting to share/HTTP in order download XML files) I would have noticed
that these files are not available to the client.

But as I said - there are extension points in the WPKG system where you could
fetch such information already. I am sure there are even much more
sophisticated tools available which _reliable_ fetch such information for you.
And such tools could do this locally even before WPKG is invoked (which might
fail already). So basic debugging like checking network connectivity should not
be done by a tool which already relies on these things to be executed (i.e.
WPKG requires these settings to be correct in order to be executed, so why
should it check it again?).

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.