On Thu, Oct 23, 2008 at 10:19 PM, David P <[EMAIL PROTECTED]> wrote: > On Thu, Oct 23, 2008 at 1:18 PM, DaZZa <[EMAIL PROTECTED]> wrote: > > useradd -c "ClamAV scann user" -d /var/clamav -u 104 -s /bin/sh clamav > > > > and then > > > > passwd clamav > > I would avoid creating another user in this situation; it looks like > he already has a "amavis" user for that purpose, but it incorrectly > has UID 105 and GID 106, whereas the ownership of the listed files is > UID 104 / GID 105. It's simpler, IMO, to edit the UID and GID of > "amavis" in /etc/passwd and /etc/group to 104 and 105 than mess around > with two users. Clam should be fine with the UID change, since the > username, rather than the UID, is specified in clamd.conf, so it > should automatically follow to the new UID.
good point, but why not just recursively chown the directory structure with the wrong UIDs so it's got the right ones? why is the passwd file the problem and not the files? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
