This one time, at band camp, Robert Millan said: > On Mon, Jan 07, 2008 at 11:24:01PM +0000, Stephen Gran wrote: > > > Whatis the output of `id clamav` on the affected system? It appears > > that you have the user but not the group, which is a "should not happen" > > kind of situation. > > At this time I have neither the user nor the group, but when this error > happened I had only the user. I'm afraid I can't explain why. All I know > is: > > - This was a long-standing sid chroot. > - It never had clamav installed before (that I can recall). > - I did "sudo apt-get install clamav", which produced this error. > > Which package is responsible for adding the group?
clamav-base. It does a fairly standard:
if [ -z "$2" ]; then
if [ -z "`getent passwd clamav`" ]; then
adduser --system --no-create-home \
--disabled-password --disabled-login \
--shell /bin/false --group --home /var/lib/clamav clamav
fi
chown clamav:clamav $DATABASEDIR
chown clamav:clamav $RUNDIR
chown clamav:clamav $LOGDIR
This can go wrong if you've removed the package but not purged it and
then delgroup'ed the group (if you purge the package, it removes both
user and group), or if even on a fresh install there is a user but no
group present. Both of those are so strange I didn't (and don't)
consider them hugely interesting cases to code around.
I just don't know how you've gotten that error. The only thing I can
think of is that you may have scripts for copying in accounts into the
chroot that fails to also copy in the groups?
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [EMAIL PROTECTED] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
signature.asc
Description: Digital signature
