As I've said in another question, I have more experience with RHEL/CentOS than I do with Ubuntu.

I've noticed that in Ubuntu, by default there is a crontab group with the GID of 102. There is no group 102 by default in CentOS. In our LDAP environment, we have a group with the ID of 102. This seems like it would cause an unpleasant conflict.

I know the best thing to do would be to change the ID of the group in LDAP, but since that has been around here longer than I have, I don't think that's going to fly. Especially since almost all of our linux boxes are CentOS (I'm just now adding our first Ubuntu boxes.)

So, my question is this: Would it be a problem if I changed the crontab group on these Ubuntu boxes from 102 to say, 113?

I plan on trying it and doing some testing, but I thought I'd throw this question out there in case anyone happens to know of any complications this would cause.

One aspect is that 'man 1 crontab' (see the "FILES" section) talks about /var/spool/cron/crontabs ownership, so if the cron daemon and related tools don't use hardcoded values but do proper lookups then changing ownership shouldn't be problematic. I'd just go and test it. If something goes belly up you can always resort to grepping the source tarball for clues.