From owner-freebsd-questions Wed May 24 11: 0:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 4A98437BC04 for ; Wed, 24 May 2000 11:00:16 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id NAA00404; Wed, 24 May 2000 13:59:53 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000524140050.00ad7b10@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 24 May 2000 14:02:55 -0400 To: "Andy Coates" , "Dan Larsson" , From: John Subject: Re: Help! :( In-Reply-To: <006e01bfc5a8$59c2cee0$2a2029d4@blade> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > | Can anyone help me out here and suggest a plan of action? > > > > I've experienced this in the past. A hit on CTRL + C > > resumes the boot. I found the problem to be name resolution > > issues. > >Hey, > >Turned out to be apache.sh script, as I installed apache with SSL recently >and it turns out the default .sh file has a line similar to: > >apachectl startssl > /dev/null > >So I started this myself, without the redirect to null, and it starts up >asking for my secure pass phrase to decrypt my SSL keys - so thats where it >was stopping and because it was being redirected to null I couldn't see it >asking this. Removed the redirection, rebooted to make sure it was that and >now as it starts asks me for my phrase to start SSL, so I can enter it and >it continues booting happily :-) > >At least I can see whats happening now, although I don't like having to >enter the phrase on bootup as I might restart this machine remotely. I'll go >read the docs and see if there's anyway around this apart from not running >it at boot. I had this same exact problem a few months back, and the 'best' solution I got from someone was to set up ssl without a passphrase (if you're worried about remote reboots). This isn't exactly the best solution, which is why I opted to keep the passphrase and not reboot remotely :) Also, the version I was playing around with would *not* let you put in null (carriage return) as your passphrase. Might be different now. Hope that helps, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message