Perl Error Log

Pablo Velasquez pablo at
Mon Apr 17 13:44:25 CDT 2000

Thanks so much for this info. I will be connecting remotely so I have to
find some solution, perhaps executing the script through SSL. The commands
are pre-determined and since the scripct goes through SSL there's no
security risk. Perhaps I can even submit the commands through  a web/SSL
form. On the other hand, I completely agree, this is a major security risk
if this script is compromised. Perhaps it's a good idea to finish all the
other redundant systems before I get to this level.

The mysql info was very handy already, thanks to everyone who sent info.

In case anyone installs the ActiveState Perl 5.6.0 I had to completely
uninstall my previous version, then actually delete the "c:\Perl" folder
also, before 5.6 would install completely. I'm using NT and have build 522

In case anyone is into T-Shirts, this has a cool Perl t-shirt:


I hope I don't seem like I'm taking and not giving Perl to the mailing-list
:) but I have another question. When I use NT, there is an error log in the
"c:\Perl" folder for PerlScript. However, for basic perl errors (aside from
the screen) is there a "log of errors"? For example, MySQL has it's own log,
Apache has a log for errors, does Perl have a log? I've been looking but I
can't find one...I guess could just write one but I'm practicing Virtue 1 :)



This message is for the named person's use only.  It may contain
confidential, proprietary or legally privileged information.  No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender.  You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended

----- Original Message -----
From: <sinck at>
To: <phoenix-pm-list at>
Sent: Monday, April 10, 2000 4:06 PM
Subject: Re: kill mysqld :)

> \_ Write a script to do whatever you want and use Net::Telnet to log into
> \_ machine and run your script, or just run the commands individually.
> \_
> \_ Hell with Net::Telnet you can even log in and 'su' to root
> MMMmm, telnet, bare passwords, mmmm.....
> Oh wait, that must have been a daydream.  Telnet is perfectly safe if
> you're not leaving the box, right?
> Of *course* it is.
> Here's hoping for Net::SSH....
> David

More information about the Phoenix-pm mailing list