Great Circle Associates Majordomo-Users
(July 1998)
 

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

Subject: Re: autocache not working
From: Bill Houle <Bill . Houle @ SanDiegoCA . NCR . COM>
Date: Tue, 28 Jul 1998 15:36:47 -0700
To: Paul Wolstenholme <wolstena @ sfu . ca>
Cc: majordomo-users @ GreatCircle . COM
In-reply-to: <199807281850.LAA06541@beaufort.sfu.ca>
References: <199807281429.HAA01357@ssol020.sandiegoca.ncr.com>

At 11:50 AM 7/28/98 -0700, Paul Wolstenholme wrote:
>
>The autocaching still doesn't work but works fine as a cron job.

Check out the mj_build_alias support for mj_background_tasks. This is what
I use instead of the autocache. Between this secondary script and a
periodic cron job, we get pretty timely synchronization.

>One other thing I just noticed when I went to delete a list using 
>Majorcool was an error message from mj_build_aliases:

What does the 'find' command (in mj_build) do when you run at the shell?
Could just be a difference between your OS' find and mine (SunOS). Also, if
you are doing -f (force) as claimed, then according to the code, the only
way that branch would fail is if the $aliases file was not readable by the
process. This seems pretty unlikely!??

--bill



Follow-Ups:
References:
Indexed By Date Previous: Re: Can I require a subject: ?
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Passwords in MJ
From: Bill Houle <Bill.Houle@SanDiegoCA.NCR.COM>
Indexed By Thread Previous: Re: autocache not working
From: Paul Wolstenholme <wolstena@sfu.ca>
Next: Re: autocache not working
From: Paul Wolstenholme <wolstena@sfu.ca>

Google
 
Search Internet Search www.greatcircle.com