I'd like to be able to remotely observe my server's hardware health. I'd like to see my motherboard hardware sensors output from sysctl: $sysctl hw.sensors and I'd like to check on my RAID status with $sudo raidctl -s raid0
But... to get an web shell script (/var/www/cgi-bin/sensors.sh) containing sysctl hw.sensors to work, I had to turn off chroot (starting httpd with "-u") (BTW using OBSD3.7-amd64) I saw the FAQ about chroot (www.openbsd.org/faq/faq10.html#httpdchroot) so I see the basics of what is required to move things into a chroot. So I was hoping to get opinion on: 1. Is there an easier way to remotely observe such hardware status? 2a. Is NOT chroot such a bad security hole vs. 2b. would converting sysctl to a apache chroot setup be even feasible? (I'm guessing not even possible considering it accesses the kernel) 3. To run raidctl, I have to sudo, since /dev/raid0a* permissions are crw-r----- Is there a better way to view the RAID status over the web, vs. what are the security risks of changing the permission of /dev/raid0* Thanks for your thoughts. dmaus
