On 16/12/13 12:59, [email protected] wrote:
> even after failed amavisd start, where 'ls socket_file' fails:
>
> # ls /var/spool/amavisd/clamd.sock
> ls: cannot access /var/spool/amavisd/clamd.sock: No such file or directory
>
> 'lsof' still shows /var/spool/amavisd/clamd.sock as valid ?
Sounds like a chroot issue. As root, what does /proc/<pid of clamd>/cwd
point to?
Cheers,
--
Steve
"...In the UNIX world, people tend to interpret `non-technical user'
as meaning someone who's only ever written one device driver."
- Daniel Pead
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
