From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: automatic system info tool? |
Date: | 2006-07-17 13:06:34 |
Message-ID: | 44BB8B5A.4080807@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I'm fairly familiar with it :-)
The trouble is that it gives info set at the time perl was compiled,
which doesn't help with the problem where a machine has been upgraded.
For example, on this FC3 machine it reports a different kernel version
from the one I have upgraded to, not surprisingly.
So what I need if possible is a runtime tool to detect the info we need.
cheers
andrew
Martijn van Oosterhout wrote:
>On Sun, Jul 16, 2006 at 06:49:26PM -0400, Andrew Dunstan wrote:
>
>
>>We also classify buildfarm machines by <os, os_version, compiler,
>>compiler_version> and config.guess doesn't give us that, unfortunately.
>>
>>
>
>It would seem to be a lot easier to use the values from perl itself,
>given you're already using it:
>
># perl -MConfig -e 'print "os=$Config{osname}, osvers=$Config{osvers}, archname=$Config{archname}\n"'
>os=linux, osvers=2.6.15.4, archname=i486-linux-gnu-thread-multi
>
>If you look at perl -V it give you a subset of useful values, probably
>a lot nicer than munging config.guess. It'll even tell you the size of
>of the C datatypes if you're interested :)
>
>Have a nice day,
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-07-17 13:08:54 | Re: plPHP and plRuby |
Previous Message | Greg Sabino Mullane | 2006-07-17 11:48:37 | Re: url for TODO item, is it right? |