Re: automatic system info tool?

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 14:16:16
Message-ID: 20060717141616.GC30221@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 17, 2006 at 09:06:34AM -0400, Andrew Dunstan wrote:
>
> 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.

Hmm. The osname and archname might still be useful, but the rest could
be out of date.

> So what I need if possible is a runtime tool to detect the info we need.

On UNIX systems uname may work pretty well. But I guess each system may
have slightly different options. What'll probably happen is that you
end up with a big if() statement testing $Config{osname} wtih each case
having specific code to determine the specifics. But for that you need
information. How do you get the currently running release of windows
for example?

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-07-17 14:52:31 Re: plPHP and plRuby
Previous Message MotherMGA 2006-07-17 13:48:31 Possible Typecasting Bug with coalesce()