responsible Windows 95/98 program

That's a kong-an in itself.

Cheers,
KM

Or, if you don't think it needs to be addressed in the middle of the night, to your email.

If you cannot do either, well there are bigger problems out there right now, you probably don't matter...

For cron jobs I send email by printing to STDERR or STDOUT. Pages require work.

{groan/grin}

-- Randal L. Schwartz, Perl hacker

neophyte

You log it to the Emergency Back-Up Logfile (c). If that doesn't work, log both of those errors to your Emergency Back-Up LogFile Logfile (c) ad infinitum...

Hmm, so the truly paranoid-but-clueless might do this:

use FileHandle;
to_logfile($message) or to_backup_logfile($message, $logfilename);

sub to_backup_logfile {
    my ($message, $logfilename) = @_;
    my $bulog = new FileHandle "$logfilename.bak" or 
        to_backup_logfile("Couldn't write $message to $logfilename!", 
+"$logfilename.bak");
    print $bulog $message;
}
[download]

Well, I suppose this code might tell you *something* useful =)

Update I was viewing turnstep's reply, below, in Mozilla M18 and everything after my <code> tag got deleted. Curse the developing lizard, but praise the project!

Actually, I started to write, but then resisted, a recursive subroutine that keeps opening (randomly named?) error files, and passing the names of all the previous error logs that it could not open until we run out of memory. Then maybe *that* error message will show up somewhere. :)