[check_postgres] problem parsing output in check_fsm_relations and check_fsm_pages

[Luke Koops]

Regarding the $HOME directory issue.  The HOME variable is not set.  See here for a conservative list of environment variables that can be used:  http://support.microsoft.com/kb/100843

I just commented out the reference to $ENV{HOME}.  The fix would be to concatenate HOMEDRIVE and HOMEPATH.

Other notes:
A few of the checks would need some work, for example drive_space which depends on the 'du' command.  Our application already had drive space monitoring built in so we didn't fix it.

The $PSQL variable couldn't handle spaces and I had trouble getting them escaped properly so I just used the DOS short path.

-Luke
-----Original Message-----
From: Greg Sabino Mullane [mailto:greg at endpoint.com] 
Sent: Tuesday, March 02, 2010 11:23 AM
To: Luke Koops
Cc: 'check_postgres at bucardo.org'
Subject: Re: [check_postgres] problem parsing output in check_fsm_relations and check_fsm_pages

On Thu, Aug 27, 2009 at 05:10:59PM -0400, Luke Koops wrote:
>    I am using strawberry perl version v5.10.0 built for
>    MSWin32-x86-multi-thread
> 
>    To run this on Windows I had to make a small change in handling the
>    $HOME directory, but that's not the issue.

Can you elaborate? We'd like to get that fixed up.

>    in check_fsm_pages and check_fsm_rlations, the query return value isn't
>    getting parsed properly.
...
>    while ($db->{slurp} =~ /\s*(\d+) \|\s+(\d+) \|\s+(\d+)\s*/gsm) {

Applied!

>    Is there any interest in making this tool run on Windows?

Yes, but I suspect the pool of developers running Windows versus Unix is very small.

>    Is this change going to break anything on Unix/Linux?

I don't think so, but it's going to be a part of the next version, so we'll find out. ;)

--
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8