i dont find it unreasonable to write full perl programs that make no assumptions about what systems they run on whatsoever... actually, that's one of its real strengths and the reason many commercial applications and many inhouse tools were written in it. it can bridge systems flawlessly because it has its own library of functions.

there are multiple CPAN modules for uptime/load, i had a look at some of them. there are a couple of reasons why i would prefer not to use them:

1. they have no corresponding packages in most operating systems (only the most used/famous ones have) and would create overhead in system admininstration.
2. they use exactly the same unportable techniques like using sysctl and /proc and so on

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.