>
> I've changed order of initialization now. I've also removed
> some debug output
> for query mode to work around the issue as some information
> is only queried for
> debug purposes.
>
> I did run both, your use-case as well as a wpkg-test suite
> run with 1.2.1-RC34
> which completed su
Hi Stefan,
On 22.10.2011 17:36, Stefan Pendl wrote:
Problem still persists, configuration sent privately (~3MB).
Verified. Sorry for delay but it took a bit to track it down and solve it as it
needs some fundamental initialization changes.
The reason is that WPKG during initialization print
>
> On 22.10.2011 17:23, Stefan Pendl wrote:
> > There still seems to be something wrong with the package
> application during a query.
>
> "Something" is a bit too unprecise... However I found that
> /query:l did show now
> the remote information as read from the settings file. This
> is fix
>
> On 22.10.2011 17:23, Stefan Pendl wrote:
> > There still seems to be something wrong with the package
> application during a query.
>
> "Something" is a bit too unprecise... However I found that
> /query:l did show now
> the remote information as read from the settings file. This
> is fix
Hi Stefan,
On 22.10.2011 17:23, Stefan Pendl wrote:
There still seems to be something wrong with the package application during a
query.
"Something" is a bit too unprecise... However I found that /query:l did show now
the remote information as read from the settings file. This is fixed in
1
>
> On 22.10.2011 16:32, Stefan Pendl wrote:
> > I have just checked the remote query and it works great
> except for one thing.
> > It seems that the queryMode does not update the host os attributes.
>
> Actually I found this to be likely a caching issue. All host
> information are
> supposed
Hi Stefan,
On 22.10.2011 16:32, Stefan Pendl wrote:
I have just checked the remote query and it works great except for one thing.
It seems that the queryMode does not update the host os attributes.
Actually I found this to be likely a caching issue. All host information are
supposed to be sta
>
> To work around this issue I've introduced a new switch called
> /queryMode which
> takes the "remote" attribute: /queryMode:remote
>
> In "remote" mode WPKG will change its behavior in some special cases:
>
> - WPKG reads all host attributes from the settings node (wpkg.xml)
> - WPKG does
Hi Stefan,
On 22.10.2011 13:03, Stefan Pendl wrote:
You need some sleep too, don't you ;-)
Sometimes yes ;)
I will give the new release a whirl in my test environments.
Great, Thank you!
Rainer
-
wpkg-users mailing l
Hi Rainer,
>
> Oh, it's 3:30am now, I guess I've broken a lot in the code,
> but we have SVN.
> Talk to you tomorrow...
>
You need some sleep too, don't you ;-)
I will give the new release a whirl in my test environments.
---
Stefan
-
Hello again,
On 22.10.2011 01:37, Rainer Meier wrote:
I've implemented /query:s and /query:l to query these tags from the (l)ocal host
or the (s)ettings database and print it on screen. So a reporting tool could
point it to a settings file using /settings: /query:s to fetch all host
attributes.
Hi Stefan,
I've implemented /query:s and /query:l to query these tags from the (l)ocal host
or the (s)ettings database and print it on screen. So a reporting tool could
point it to a settings file using /settings: /query:s to fetch all host
attributes.
NEW: Implemented new query parameters:
> >
> > Sure it would be much easier, if we could use a command
> line switch for this.
> > In addition we would need another command line switch,
> which instructs wpkg.js to retrieve the host attributes from
> the specified
> > wpkg.xml file instead of the current host.
> >
>
> Too slow
>
Hi Stefan,
On 21.10.2011 20:39, Stefan Pendl wrote:
There is no easy solution for this yet.
You can specify a server-side copy of the local "database" of any client for
examination by using the /config: switch to a
config.xml file, which only contains the "settings_file_name" and
"settings_fi
Hi Kai,
On 21.10.2011 18:14, Kai Pastor wrote:
Hello,
I am testing WPKG 1.2.1-RC27 and have not seen any problems. Thank you very much
for your work.
Great news.
So far I have also used WPKG Create Report which is linked on the download page.
This useful tool is not yet aware of the new fe
>
> So far I have also used WPKG Create Report which is linked on the
> download page. This useful tool is not yet aware of the new
> features and
> the changes in the syntax. I guess that will take quite some
> effort and
> time for implementing an update to this tool.
>
I have been in cont
Hello,
I am testing WPKG 1.2.1-RC27 and have not seen any problems. Thank you
very much for your work.
So far I have also used WPKG Create Report which is linked on the
download page. This useful tool is not yet aware of the new features and
the changes in the syntax. I guess that will take
17 matches
Mail list logo
