Re: [wpkg-users] Ugly perl script to check if packages are installed on a set of workstations.
Hello Chris, I was going to wait, and clean up this script, but I don't think I will ever come back to it. ... I use this program to send a list to our desktop techs about which computer are out of compliance. I would love any feedback or improvements from anyone, or if you have a better way to get this type of information. Thanx again for this nice script, it does it's work - and this is worth the effort. But I have one problem with the script, perhaps you can help me. If I have two hosts definitions in hosts.xml, one special for a certain host and one with regex for all common hosts, the report.pl prints out the special host missing the remaining packages from the common profile which shouldn't be installed on the special host. To be clearer - an example: profile1: packages common to all hosts profile2: packages for the special host without e.g. acrobat8 which is included in profile1 for the common hosts hosts definitions: host name=ws-0026 profile-id=profile2 / ... host name=ws-.+ profile-id=profile1 / report.pl gives: WS-0026: acrobat8 DBv: 5 PCv: Any hints? thanx in advance Falko -- Falko Trojahn fon +49-341-3581294 Dipl-Ingenieur Netzwerke/Support fax +49-341-3581295 SMI Softmark Informationstechnologien GmbH Sitz: D-04416 Markkleeberg, Friedrich-Ebert-Str. 51 Registergericht: Amtsgericht Leipzig HRB 164 Geschäftsführer: Andreas Griesmann - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Ugly perl script to check if packages are installed on a set of workstations.
Hello Gerd, Your report.pl is not ugly, it's pretty pretty! Works fine for me after adjusting the locations, even if perl -W (v5.8.8) is saying: Using a hash as a reference is deprecated. BTW. If I copy the statusfiles to a share using a wpkg-package like http://wpkg.org/Viewing_software_installed_on_workstations , I always get the status *before* the last execution of wpkg.js. Perhaps the better way ist to define an additional action to execute after wpkg.js. you could use the post-execution script in WPKG Client (execute after), or an xcopy ... line in your wpkg-start.bat. HTH Falko Chris Crow schrieb: I was going to wait, and clean up this script, but I don't think I will ever come back to it. This script needs to be copied to the root of the wpkg share, and it evaluates the following locations: hosts/*.xml packages/*.xml profiles/*.xml status/*.xml (status is the directory where I copy the wpkg.xml files from all of the workstations) When you run the script, it will evaluate the list of packages that should be installed with the packages that are install on each computer in the status directory. It then prints the differences. If the program gives no output, then everything is up to date. I use this program to send a list to our desktop techs about which computer are out of compliance. I would love any feedback or improvements from anyone, or if you have a better way to get this type of information. Thanks, Chris - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users -- Falko Trojahn fon +49-341-3581294 Dipl-Ingenieur Netzwerke/Support fax +49-341-3581295 SMI Softmark Informationstechnologien GmbH Sitz: D-04416 Markkleeberg, Friedrich-Ebert-Str. 51 Registergericht: Amtsgericht Leipzig HRB 164 Geschäftsführer: Andreas Griesmann -- Falko Trojahn fon +49-341-3581294 Dipl-Ingenieur Netzwerke/Support fax +49-341-3581295 SMI Softmark Informationstechnologien GmbH Sitz: D-04416 Markkleeberg, Friedrich-Ebert-Str. 51 Registergericht: Amtsgericht Leipzig HRB 164 Geschäftsführer: Andreas Griesmann - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Ugly perl script to check if packages are installed on a set of workstations.
Hi, Your report.pl is not ugly, it's pretty pretty! Works fine for me after adjusting the locations, even if perl -W (v5.8.8) is saying: Using a hash as a reference is deprecated. BTW. If I copy the statusfiles to a share using a wpkg-package like http://wpkg.org/Viewing_software_installed_on_workstations , I always get the status *before* the last execution of wpkg.js. Perhaps the better way ist to define an additional action to execute after wpkg.js. Greetings, Gerd Chris Crow schrieb: I was going to wait, and clean up this script, but I don't think I will ever come back to it. This script needs to be copied to the root of the wpkg share, and it evaluates the following locations: hosts/*.xml packages/*.xml profiles/*.xml status/*.xml (status is the directory where I copy the wpkg.xml files from all of the workstations) When you run the script, it will evaluate the list of packages that should be installed with the packages that are install on each computer in the status directory. It then prints the differences. If the program gives no output, then everything is up to date. I use this program to send a list to our desktop techs about which computer are out of compliance. I would love any feedback or improvements from anyone, or if you have a better way to get this type of information. Thanks, Chris - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Ugly perl script to check if packages are installed on a set of workstations.
I was going to wait, and clean up this script, but I don't think I will ever come back to it. This script needs to be copied to the root of the wpkg share, and it evaluates the following locations: hosts/*.xml packages/*.xml profiles/*.xml status/*.xml (status is the directory where I copy the wpkg.xml files from all of the workstations) When you run the script, it will evaluate the list of packages that should be installed with the packages that are install on each computer in the status directory. It then prints the differences. If the program gives no output, then everything is up to date. I use this program to send a list to our desktop techs about which computer are out of compliance. I would love any feedback or improvements from anyone, or if you have a better way to get this type of information. Thanks, Chris report.pl Description: Perl program - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Ugly perl script to check if packages are installed on a set of workstations.
Hi Chris, Chris Crow wrote: I was going to wait, and clean up this script, but I don't think I will ever come back to it. There is always too less time - or too many ideas... This script needs to be copied to the root of the wpkg share, and it evaluates the following locations: hosts/*.xml packages/*.xml profiles/*.xml status/*.xml (status is the directory where I copy the wpkg.xml files from all of the workstations) When you run the script, it will evaluate the list of packages that should be installed with the packages that are install on each computer in the status directory. It then prints the differences. If the program gives no output, then everything is up to date. I use this program to send a list to our desktop techs about which computer are out of compliance. I would love any feedback or improvements from anyone, or if you have a better way to get this type of information. Thanks a lot for your work. From the first (quick) look it seems to be quite a clean script which could help sysadmins. In fact I plan to add such scripts to a kind of 3rd-party-tools folder within the WPKG distribution. However I would like to have at least a short README which describes what it is doing and how to use it. I know this is the annoying part but I think just including this script is quite useless if nobody knows what it is doing and how to use it. You might add some basic usage comments to the header and a small README. For your script it might even need some more documentation as it implies that you have a package with execute=always flag running which copies the local wpkg.xml to the server share. So a how-to-setup section within the README is absolutely mandatory. I hope you can find some time to add these things. br, Rainer - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
