User Tools
retain_dhcp_lease_info_after_a_reboot
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| retain_dhcp_lease_info_after_a_reboot [2023/08/09 15:39] – [Method 2: Copying the lease database to permanent storage at halt time] -clarify Method 2 uses both sets of lines hogwild | retain_dhcp_lease_info_after_a_reboot [2023/08/15 18:32] (current) – [Method 2: Copying the lease database to permanent storage at halt time] petervdm | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| - Use a path relative to your own system. | - Use a path relative to your own system. | ||
| - Using permanent storage means client devices won't lose connectivity if the router reboots. Because the lease database is not stored in RAM, a reboot won't erase it. This can be useful, for example, when devices are connected to a switch. Moreover, clients won't display in the [[status-devices|Device List]] as having an active lease until their current lease expires, and they' | - Using permanent storage means client devices won't lose connectivity if the router reboots. Because the lease database is not stored in RAM, a reboot won't erase it. This can be useful, for example, when devices are connected to a switch. Moreover, clients won't display in the [[status-devices|Device List]] as having an active lease until their current lease expires, and they' | ||
| - | - You will notice | + | - Notice |
| Line 28: | Line 28: | ||
| <code -> | <code -> | ||
| [ -f / | [ -f / | ||
| - | sort -b -k 2 -u -z / | + | sort -b -k 2 -u -z / |
| - | sort -b -k 2 -u -z / | + | sort -b -k 2 -u -z / |
| - | diff -a /tm | + | diff -a /tmp/ |
| - | kill -HUP `ps | grep | + | kill -HUP `ps | grep -E [d]nsmasq | awk '{ print $1 }'` |
| - | rm / | + | rm / |
| - | rm / | + | rm / |
| + | rm -f / | ||
| } | } | ||
| </ | </ | ||
retain_dhcp_lease_info_after_a_reboot.1691591955.txt.gz · Last modified: 2023/08/09 15:39 by hogwild
Page Tools
