Skip Menu |

Download (untitled) / with headers
text/plain 1.7KiB
From Thu Apr 20 02:58:31 2000
by (8.9.3/8.9.3) with SMTP id CAA20687
for <bugs@RT-11.MIT.EDU>; Thu, 20 Apr 2000 02:58:30 -0400 (EDT)
Received: from by MIT.EDU with SMTP
id AA09199; Thu, 20 Apr 00 03:00:24 EDT
Received: from by (8.9.1/8.9.1) with ESMTP id LAA11220
for <>; Thu, 20 Apr 2000 11:01:25 +0400 (????)
Message-Id: <>
Date: Thu, 20 Apr 2000 10:59:51 +0400
From: Max Kluev <>
To: krb5-bugs@MIT.EDU
Subject: Starting kerberos daemon by initd

Show quoted text
>Number: 846
>Category: krb5-kdc
>Synopsis: Starting kerberos daemon by initd
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: krb5-unassigned
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Apr 20 02:59:01 EDT 2000
>Last-Modified: Sat Jun 23 01:38:31 EDT 2001
>Originator: Max Kluev <>
Dear kerberos5 development group.

I try to start krb5kdc by initd with option "respawn" in inittab on Solaris 7 OS.
And I see that fist start process of krb5kdc fork child and ends. After that initd starts krb5kdc again.

Do you know any standard way to start krb5kdc via initd with checking of process life?
What was the reason to keep child and ends main process and may I change this bechaviour?

Thank you for you time.

Best wishes
Max Kluev
Show quoted text

Responsible-Changed-From-To: gnats-admin->krb5-unassigned
Responsible-Changed-By: raeburn
Responsible-Changed-When: Sat Jun 23 01:38:30 2001

Show quoted text
Closing old support question.