> Weird. Are you *sure* the umask is 002? Yep. I type umask at the shell (csh, Bash) and get "2".
> - People run "cvs ci" via a script that's messing with > the umask Verified that the binary is running. > - commitinfo or other triggers (not sure if this could have > an effect, but it's worth checking) > - If you're using the watch/edit stuff, maybe that could affect > it? Not using these. > - A local patch to CVS Possible, but no record of a local change. Only way to be sure will be rebuilding from scratch. Thought I'd ask if it's known behaviour first. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs