From: Phil Doroff [mailto:[EMAIL PROTECTED]
>>
>> Ok, noted. I deleted all the tmp files out, and watched as more were
>> created (as users POP'ed in). They were owned by root, and all were 0
>> bytes. Just blank files. I then changed the inetd line to
>> launch pop3d under vpopmail.vchkpw, and these files were still
created,
>> just with vpopmail.vchkpw ownership. Also of interest is that an
>> open-smtp.lock file is created under whichever user pop3d is run
under,
>> and does not get cleared... hrm.
>Leave it running as vpopmail, that's better. The lock file is normal.
>What are the permissions on the files in that directory?
Ok, set the inetd line to vpopmail.vchkpw
The permissions are:
drwxr-xr-x 2 vpopmail vchkpw 748k Jun 26 17:20 .
drwxr-xr-x 8 root staff 4.0k Apr 15 17:51 ..
-rw-r--r-- 1 vpopmail vchkpw 25 Jun 18 04:21 inc_deps
-rw-r--r-- 1 vpopmail vchkpw 32 Jun 18 04:21 lib_deps
-rw-r--r-- 1 vpopmail vchkpw 0 Jun 26 11:52 open-smtp
-rw-r--r-- 1 vpopmail vchkpw 0 Jun 26 17:20 open-smtp.lock
-rw-r--r-- 1 vpopmail vchkpw 0 Jun 26 17:20 open-smtp.tmp.8893
-rw-r--r-- 1 vpopmail vchkpw 180 Jun 18 04:28 tcp.smtp
-rw-r--r-- 1 vpopmail vchkpw 31k Jun 26 11:52 tcp.smtp.cdb
and the directory itself:
drwxr-xr-x 2 vpopmail vchkpw 748k Jun 26 17:22 etc
Needless to say, I'm still a bit baffled. :)
Thanks much for all the help!
-Phil
