Rc.conf or other boot scripts… some insight?



  • Hello again, ;D

    I need some help deciphering pfSense's internals. I'm trying to figure out why my /usr/local/etc/php.ini keeps reverting to defaults (and chopping out my mysql.so extension line - I'm guessing by reverting) every time I reboot the box. It's quite annoying, as I have to edit the file, kill lighttpd, then restart it after remembering where lighty-webconfigurator.conf is stored - this file system really irritates me.

    So I'm trying to start from cold boot and work my way up, much the same as I read a PHP script from the requested-page outward to find the solution to a problem. So far I've gotten nowhere, as rc.conf doesn't exist - a feat deemed seemingly impossible by the FreeBSD world!

    I read that pfSense is booted entirely from PHP, which I don't believe for a quarter of a millisecond. First of all, that doesn't explain why php.ini is getting reverted. Second, there's got to be a way to interpret the script first, so how can it read PHP without having booted first? There is a lot of boot stuff that goes on before pfSense evidently takes over the boot process, so… where's it done?

    If you'd just like to cut to the point and solve my problem, I need to figure out how to keep php.ini from getting rewritten every time I need to reboot (rather frequently as it gets more and more unstable with crashed/disconnected SSH sessions that had running, now orphaned, processes... etc...). However, I really would like to learn more about how pfSense works differently than FreeBSD. It might help me even get my services (MySQL and Samba) to auto-start on boot! ;)

    (edit: I'm using the developer version of pfSense, and I'm running those services because I'm more concerned about functionality than security - reader's digest version. I'd also love to get rid of that pesky "WITNESS" kernel option in the near future, but...)



  • On my stock 1.2release box php.ini doesn't get re-written on boot.



  • Hm, I also noticed by accident, thanks to the arse-backwards filesystem (bangs head against desk), that there are two php.ini files - the in-use one actually being in /usr/local/lib/php.ini, and another one in /usr/local/etc/php.ini. Not sure what the purpose of that is, but I'm going to guess that if I reboot after having mistakenly made my boot-time edit to ./etc/php.ini, I may now have my problem sort-of solved. Not one to reboot my gateway on a whim though, so I guess it'll have to wait til the next reboot. =P


Log in to reply