Shibboleth Developers

[Dan Pritts <>]

whoops.  I had meant it to be every two hours on the 23rd minute.
i'm glad i sent you the crontab entry rather than telling you what
[i thought] i'd done or it would have taken longer to figure it out.

The expense is not in the bandwidth but in churning the disks to figure
out what's changed.  

that said i've set it to hourly.

On Fri, Nov 19, 2004 at 11:16:09AM -0600, Walter Hoehn wrote:
> Can we change this to run every hour?  Most hours it should be pretty 
> inexpensive, I would think.
> 
> When I put in a bug fix I usually ask the reporter to checkout the 
> updated code from cvs and test it in their environment.  This would be 
> a much smoother process if I could say "wait an hour" instead of "wait 
> until tomorrow".
> 
> -Walter
> 
> 
> On Sep 3, 2004, at 4:32 PM, Dan Pritts wrote:
> 
> >[root@ellis
> > root]# crontab -l
> ># DO NOT EDIT THIS FILE - edit the master and reinstall.
> ># (/tmp/crontab.9637 installed on Mon Aug  2 14:24:11 2004)
> ># (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp 
> >$)
> >*/2 23 * * * /usr/local/pkg/local-scripts/sbin/rsync-cvs
> >
> >
> >On Fri, Sep 03, 2004 at 04:20:44PM -0500, Walter Hoehn wrote:
> >>Hi Dan,
> >>
> >>How often is the prod cvs synched over to the anonymously accessible
> >>copy?
> >>
> >>-Walter
> >>
> >
> >
> >danno
> >--
> >dan pritts                                       
> >
> >systems administrator                            734/352-4953 office
> >internet2                                        734/834-7224 mobile




danno
--
dan pritts - systems administrator - internet2
734/352-4953 office        734/834-7224 mobile