Great Circle Associates Majordomo-Users
(December 1998)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: sh: list-digest-outgoing: command not found
From: Ajay Sharma <ssharma @ odc . net>
Date: Tue, 29 Dec 1998 02:41:30 -0800 (PST)
To: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Cc: majordomo-users @ GreatCircle . COM
In-reply-to: <ufaww3bbxhf.fsf@epithumia.math.uh.edu>


I added the line of code to my script and this is what is reported:

>>>> mkdigest excellent-digest wwamcs
producing Excellent Digest V1 #12
        processing /var/lib/majordomo/digest/excellent-digest/001
        $mailer is '/usr/sbin/sendmail -oi -oee -f$sender'
        $mailcmd is '/usr/sbin/sendmail -oi -oee -fowner-excellent@odc.net
'.
sh: excellent-digest-outgoing: command not found
>>>> end
END OF COMMANDS

As you can see it added a newline at the end of the $mailcmd (after the
eval).  I added a "chop($mailcmd);" in the script right above the system
command and I finally got my first digest.  I never thought about actually
going into the code and editing it myself, I always figured that if it
broke on me, then it was broken for everyone else and it would've been
fixed.  Oh well, a very cool learning experience.  

later,
ajay

On 28 Dec 1998, Jason L Tibbitts III wrote:

> >>>>> "AS" == Ajay Sharma <ssharma@odc.net> writes:
> 
> AS> Is there anything else you'd like to see to help with the problem like
> AS> the majordomo.cf or the /etc/aliases files?
> 
> Yes, of course all pertinent information helps.  I assume you have access
> to the source; it might be useful to insert some debugging code in the
> digest script to see what's going on.
> 
> The only place in the digest script that I can possibly imagine that this
> error could come from is here:
> 
>     if ($opt_d) {
>         warn "digest output in $TMPDIR/testdigest.$NUMBER\n";
>     } else {
>         $sender = $V{'ERRORS-TO'};
>         $mailcmd = eval qq/"$mailer"/;
>         system("$mailcmd $V{'REALLY-TO'} < $DIGEST");
>         unlink(@processed);
>     }
> 
> so if $mailcmd is somehow empty, the script will try to call
> $V{'REALLY-TO'} (which should be listname-digest-outgoing) as a command.
> Bad, but it would explain why sh is telling you that
> listname-digest-outgoing isn't a legal command.
> 
> So what is $mailer set to in majordomo.cf?  How about adding a line like
> 
> print STDERR "\t\$mailer is '$mailer'; \$mailcmd is '$mailcmd'.\n";
> 
> just before that system() call?
> 
>  - J<
> 

-----------------------------------------------------
Satyajot (Ajay) Sharma 
http://www.odc.net/~ssharma/ 
http://www.odc.net/excellent/ <- Excellent Online
ICQ: 13783075 
------------------------------------------------------




References:
Indexed By Date Previous: Re: Upgrade screwed up digest.
From: Ben Smithurst <ben@scientia.demon.co.uk>
Next: Re: @#$%^ Permissions - help please
From: "Peter Seitz" <seitz@bzs.tu-graz.ac.at>
Indexed By Thread Previous: Re: sh: list-digest-outgoing: command not found
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: @#$%^ Permissions - help please
From: Alan A Hodson <bearsysop@linuxbear.elpaso.k12.tx.us>

Google
 
Search Internet Search www.greatcircle.com