dovecot 4.1 port won't fork

Dovecot on a new 4.1 cvs install with 4.1 dovecot port will
not fork any ideas..
here is kdump 
[...]
 3918 dovecot  RET   sigprocmask -65793/0xfffefeff
  3918 dovecot  CALL  dup2(0x4,0)
  3918 dovecot  RET   dup2 0
  3918 dovecot  CALL  dup2(0x4,0x1)
  3918 dovecot  RET   dup2 1
  3918 dovecot  CALL  sigprocmask(0x1,0xffffffff)
  3918 dovecot  RET   sigprocmask 0
  3918 dovecot  CALL  mprotect(0x3c007000,0x1000,0x3)
  3918 dovecot  RET   mprotect 0
  3918 dovecot  CALL  mprotect(0x3c007000,0x1000,0x1)
  3918 dovecot  RET   mprotect 0
  3918 dovecot  CALL  sigprocmask(0x3,0)
  3918 dovecot  RET   sigprocmask -65793/0xfffefeff
  3918 dovecot  CALL  fork()
  3918 dovecot  RET   fork 14942/0x3a5e
  3918 dovecot  CALL  sigprocmask(0x1,0xffffffff)
  3918 dovecot  RET   sigprocmask 0
  3918 dovecot  CALL  mprotect(0x3c007000,0x1000,0x3)
  3918 dovecot  RET   mprotect 0
  3918 dovecot  CALL  mprotect(0x3c007000,0x1000,0x1)
  3918 dovecot  RET   mprotect 0
  3918 dovecot  CALL  sigprocmask(0x3,0)
  3918 dovecot  RET   sigprocmask -65793/0xfffefeff
  3918 dovecot  CALL  exit(0)

On 7/6/07, dreamwvr <dreamwvrdreamwvr.com> wrote:
> Dovecot on a new 4.1 cvs install with 4.1 dovecot port
will not fork any ideas..
> here is kdump
...
>   3918 dovecot  CALL  fork()
>   3918 dovecot  RET   fork 14942/0x3a5e

That shows that fork() was successful and that the pid of
the child
was 14942.  If you want to see what the child is doing after
the fork
then you'll need to pass ktrace the -i option so that the
child
inherit the tracing.


Philip Guenther