From owner-freebsd-questions@FreeBSD.ORG Sat Nov 26 09:45:43 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B2A816A41F for ; Sat, 26 Nov 2005 09:45:43 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3CD43D55 for ; Sat, 26 Nov 2005 09:45:41 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [80.192.2.225] ([80.192.2.225]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sat, 26 Nov 2005 09:46:34 +0000 Message-ID: <43882EC1.4010408@dial.pipex.com> Date: Sat, 26 Nov 2005 09:45:37 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20051106 X-Accept-Language: en MIME-Version: 1.0 To: Jayesh Jayan References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Nov 2005 09:46:34.0359 (UTC) FILETIME=[49834070:01C5F26E] Cc: freebsd-questions@freebsd.org Subject: Re: inetd.conf becomes blank after reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2005 09:45:43 -0000 Jayesh Jayan wrote: >Hi, > >On some of the machine where I have FreeBSD 5.4, /etc/inetd.conf becomes a >blank file soon after reboot. > >I have kept a copy of the file and when the service fails after reboot I >restore the backup and restart the inetd service. > >What I need to check, to solve this issue. How can this be solved >permanently ? Please also let me know the logs which I can check to find the >exact issue. > I'm afraid that the most likely cause is something *you* did. Nothing in the system would deliberately remove that file, and if it is happening because of some misconfiguration then nothing would appear in a log file. Two things to try: 1) Find references in /etc and /usr/local/etc to inetd.conf. These are the likely places to find the problem. find /etc /usr/local/etc -type f -exec egrep -H inetd {} \; 2) Compare /etc and /usr/local/etc on the failing machines with the ones on good machines. Changing the flags on /etc/inetd.conf to prevent it being blanked should work around the symptoms, but not the cause. This should work: chflags schg /etc./inetd.conf But if you run in secure mode you'll need to go down to single-user to get rid of the flag, and you can't edit inetd.conf with the flag in place. --Alex