On Sat, 11 Jun 2005, David Leangen wrote: >Tried that. I left the service down for over an hour. Unfortunately, that >doesn't seem to make any difference.
Hi, David. Did you try netstat? $ netstat -plet This will tell you who is listening on all TCP ports on your system. Look for 993 or "imaps". This could give you a clue as to whether somebody else is occupying the port. You can also look at supervise's "helpful" log output to the process view display. If you run "ps faxwww", you'll see some debug output from supervise that usually gives some clues. Otherwise, I usually try running the service manually, but executing the "run" bash file as root. If this fails to start the service, or gives no clues, I do an strace: $ strace -o dump -s 1024 -f ./run The strace output usually reveals the culprit. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
