I ran across this when upgrading a site from 1.x to 2.x. I had forgotten
to remove the inetd.conf entries for the cyrus servers. In 2.x they
don't run from inetd, they are spawned by the master.
Hmm. Looks like you're having bigger issues than just the env
variable. Nothing come sto mind right now, but its late and I've had a
few too many pops.
e-d0uble wrote:
Applied patch and... Still no luck. Here's the log:
Jun 9 12:03:22 spicymeatball imapd: could not getenv(CYRUS_SERVICE)
Heh. I know the hic feeling, saturday nights.
Anything else I can do here?
thanks
Ken Murchison wrote:
Hmm. Looks like you're having bigger issues than just the env
variable. Nothing come sto mind right now, but its late and I've had a
few too many pops.
e-d0uble wrote:
Applied patch
Try applying the attached patch. This will keep the service from
exiting, but will still log any errors with respect to CYRUS_SERVICE.
I'd like to find out if putenv() is failing, or something else is going
on.
If you want to know how/why CYRUS_SERVICE is used, read the ACCESS
CONTROL section
Applied patch and... Still no luck. Here's the log:
Jun 9 12:03:22 spicymeatball imapd: could not getenv(CYRUS_SERVICE)
Jun 9 12:03:22 spicymeatball service-imapd[21427]: executed
Jun 9 12:03:22 spicymeatball service-imapd[21427]: unable to set close
on exec: Bad file descriptor
Jun 9
Hey all,
This should be an easy and quick question. When I try and load the imap
daemon I get the following error...
imapd: could not getenv(CYRUS_SERVICE); exiting
this also occurs for the pop3 daemon as well.
I am using redhat linux 7.1 with cyrus-imapd-2.0.14 and cyrus-sasl-1.5.24
Garrett, Michael R wrote:
Hey all,
This should be an easy and quick question. When I try and load the imap
daemon I get the following error...
imapd: could not getenv(CYRUS_SERVICE); exiting
this also occurs for the pop3 daemon as well.
I am using redhat linux 7.1 with
