Search results for query: *

great. so easy! it works well. I have another question. Maybe, you can help me again? With every execution of my perl script via cron, there is a mail with the console-output from my perl script. How can I eleminate these mails from the cron job?

Hi! Need help! I wrote a perl script which I want start with cron from a linux system. If I start the perl script in a console, it works well. The script isn`t stored in the home directory from the user. If I run my script from the cron, there are som failures that the script doesn`t find some...

I tried the line D:\Perl\bin\perl.exe "c:\test.pl > C:\testoutput.txt" There is no error in the Status-ID column, but there is also no testoutput.txt-File.

I tried the AT-command on the console. C:\>at Status-ID Tag Zeit Befehlszeile ------------------------------------------------------------Fehler 1 Morgen 12:36 PM "perl c:\test.pl > C:\testoutput.txt" There occurs an error (Status-ID...

Hi! I wrote a testscript print "hello world!" and this script would i start at 10:00 am with the "at"-command(WINNT). at 10:00 cmd /c "c:\test.pl > c:\testoutput.txt" But there is no text in the testoutput.txt. Can anyone help me?

The solution of the startproblem is to remove the variable PERLDB_OPTS="RemotePort=127.0.0.1:2000". I removed the variable with the regedit. The perl debugger works now very well.

I have now installed perl version 629. This version runs on a another machine very well. Debugging is also ok with the same scripts. The problem is locally on my machine. Every script makes the same failure. I see no entry 127.0.0.1:2000 with netstat -n. Maybe is here the problem?

Yes, i tried newer versions of perl, but there is always the same failure.

Hi! I cannot start the perl debugger. perl -d test.pl Default die handler restored. Could not create socket to connect to remote host. at D:/Perl/lib/perl5db.pl lin e 429. Compilation failed in require. BEGIN failed--compilation aborted. My OS is WinNT4.0 and here a snapshot from the system...

We have the following problem after we had updated the CW2000 on our Sun-machine: The login window can be accessed without failures. When we fill in the user and password and click "connect", there is no response at this time. Our feeling is that the user/password verification is ok...