As John Polstra wrote ...
> In article <[EMAIL PROTECTED]>,
> Wilko Bulte <[EMAIL PROTECTED]> wrote:
> > Maybe this is a stupid question and/or FAQ but:
>
> You probably should have written to [EMAIL PROTECTED] instead
> of the -current list.
Well, I was not exactly claiming this is a cvsup bug of some sorts.
> > I'm currently cvsupping updates on the CVS repository. Most of the
> > times that is a couple of minutes, but today it is already 1 hour busy.
> >
> > Mainly with:
> >
> > SetAttr <bla>
> >
> > (loads and loads of these).
> >
> > What gives?
>
> Several things can cause this:
>
> - You are running cvsup with a different umask than usual. To guard
> against this, you can add a "umask=022" setting in your supfile
> (CVSup-16.0 and later).
I ran cvsup as root, umask set to 022. But I added the umask line
to the supfile just to make sure.
> - You are running cvsup under a different user-id than usual. This
> probably has no effect unless you have "preserve" in your supfile.
> That's almost always a bad idea except for special situations.
I run it as root, and have always done so. Is this a bad idea maybe?
> - You've accidentally touched all the files in your repository in
> some way (changed their modtimes, changed their permissions, changed
> their owners, etc.).
Not that I recall having done so. But I'll keep a close eye on this.
I just gave cvsup another try and it only took a few minutes updating
some files in the repository. Which looked just fine.
Thank you for your help,
Wilko
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
