Hi the /dev/crypto requirement seems to come for free when you build apache on openBSD. Reading up on it it should fall over gracefully to software when you don't have hardware support.
I don't think this is the problem anymore because I can still run chrooted apache in non-daemon mode. Very frustrating :-( Conrad On 11/27/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: > > On Mon, Nov 27, 2006 at 07:06:51PM +0000, Conrad Winchester wrote: > > On 27 Nov 2006, at 18:22, Tom Cosgrove wrote: > > >Conrad Winchester 27-Nov-06 08:23 > > >>Secondly, an apology: I am not following the standard way of doing > > >>things, but to be honest thats the way I am. > > >> > > >>I am tryng to chroot apache 2.2 (yes I like apache 2 and have loads > > >>of experience with it, I have very little apache 1.3 experience). I > > >>have got it working in debug mode > > > >>lovely, but when I try to run it normally > > > >>it fails to daemonize itself and throws the following error > > >> > > >>[Mon Nov 27 08:09:40 2006] [crit] (6)Device not configured: > > >>apr_proc_detach failed > > >>Pre-configuration failed > > > >>I am pretty sure this is due to incorrect /dev nodes in my chrooted > > >>file system. > > > >Try using ktrace(1) and kdump(1) to see what it's try to do. > > > thanks for that. I have identified a problem with /dev/crypto. I make > > it with > > > > #mknod /server/web/dev/crypto c 70 0 > > #chmod 666 /server/web/dev/crypto > > > > but I get the following output from kdump > > > > 2603 httpd NAMI "/dev/crypto" > > 2603 httpd RET open -1 errno 6 Device not configured > > > > What is the proper way to create a /dev/crypto node? > > Pretty much this, but /dev/crypto is only for hardware-accelerated > crypto. Are you really sure you should use it? > > Also, check for the nodev mount flag. > > Finally, doing things differently isn't always a good idea, but I'm sure > you are aware of this. > > Joachim
