pfSense

Add the ability for full installs to optionally use RAM disks for /tmp and /var, and to allow selecting a size for /tmp and /var RAM disks on both Full installs and NanoBSD.
I think I caught most of the edge cases for transitioning into and out of RAM disk mode, and preserving data across reboots as is done on NanoBSD (RRD, DHCP leases, pkg/pbi info).

We no longer use /var/run/config.lock - catch up to other progress. Also, use lockf to test if the config is locked now, with a 30 second timeout.

Backup DHCP leases on NanoBSD too

Move the RRD backup code to a script.

Save the old shutdown binary in an attempt to smooth a firmware upgrade that crosses to/from 32/64-bit.

Don't kill ssh, it will stop the rest of the process when done from ssh. Instead, do not shut down network interfaces before a reboot. The original motive for doing this may no longer be necessary. Fixes #626

Send TERM to sshd during shutdown/reboot to ensure that client sessions are kicked properly. Fixes #626.

Add a space between interfaces

Backout last commit

Call save_sshkeys on reboot for nanobsd

Down interfaces before rebooting. Hopefully giving enough time
for the master interface to send a pfsync() notification to its
peers. Open and Free both down the interface before rebooting.

Woops, cd to / and then tar

cd to /var before running tar operation

MFC 12687
Silent tar: Removing leading '/' from member names on reboot

MFC 11521
Mount config area rw before tar and then ro after tar.

MFC 11520
Save the RRD files! MFC: Soon, testing with hoba now.
Tickets:

Do not reboot or halt if a config_write() operation is in progress

Add $Id$ tags

Add rc.halt command which will shutdown and halt a running system.

Suggested-by: Bachman Kharazmi

Use shutdown -r instead of reboot.

Noticed-by: Bachman Kharazmi

Initial revision