Printing a content-type is a good idea, but it won't always work -- you'll want to turn output buffering off, just in case something throws an error before the print buffer gets flushed, and even then, it might not get to the print statement if something happens in a BEGIN block. (and well, 'use' counts as a BEGIN block.

Based on the error message, I doubt it's a permissions problem, but I would make sure that the file passes 'perl -wc filename' from the command line -- it'll let you know if there's something blatently wrong with it (like missing modules, which is a distinct probability when switching systems, even when the perl versions are the same)

Oh -- and for debugging, I love CGIwrap. It handles processing limits on my CGIs and keeping them from running as the webserver, and a quick change to the URL, and it'll spit debugging info back to you.

---

---

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.