crond likes full pathnames is my first thought. Thats likely why it works
from the command line and not crond.
Tom
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,"|sendmail $recipient");
print SENDMAIL "From: WVFD EMS Dispatch
On Sun, 27 Aug 2000, Security wrote:
crond likes full pathnames is my first thought. Thats likely why it works
from the command line and not crond.
Tom
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,"|sendmail
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,|sendmail $recipient);
print SENDMAIL From: WVFD EMS Dispatch [EMAIL PROTECTED]\n;
print SENDMAIL To: WVFD EMT $recipient\n;
print SENDMAIL Subject: Possible EMS call\n;
print SENDMAIL \n;
crond likes full pathnames is my first thought. Thats likely why it works
from the command line and not crond.
Tom
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,|sendmail $recipient);
print SENDMAIL From: WVFD EMS Dispatch [EMAIL
On Sun, 27 Aug 2000, Security wrote:
crond likes full pathnames is my first thought. Thats likely why it works
from the command line and not crond.
Tom
Any ideas why the following won't actually send email when run from cron:
#!/usr/bin/perl
#
open(SENDMAIL,|sendmail $recipient);
5 matches
Mail list logo