| 1 |
On Tue, May 17, 2011 at 08:06:46PM -0400, James Cloos wrote: |
| 2 |
> >>>>> "MC" == Markos Chandras <hwoarang@g.o> writes: |
| 3 |
> |
| 4 |
> MC> Can you please provide some examples that require /var/lock to |
| 5 |
> MC> survive a reboot? |
| 6 |
> |
| 7 |
> Not everything is part of the distribution. |
| 8 |
> |
| 9 |
> The one which first comes to mind are lock files placed to prevent |
| 10 |
> certain cron-initiated jobs from running right after a reboot. |
| 11 |
> |
| 12 |
> Or locks preventing certain daemons from accepting connections. |
| 13 |
> |
| 14 |
> Such locks often are used to protect net bandwidth when it is needed |
| 15 |
> for real-time use. A reboot of some random box on the lan should not |
| 16 |
> break such locks. |
| 17 |
|
| 18 |
According to what I am reading in the fhs, /var/lock is not sharable |
| 19 |
between multiple systems. Also, the contents of the lock file is |
| 20 |
supposed to be the pid of the process that holds the lock [1]. |
| 21 |
|
| 22 |
Given that, a lock will automatically be invalid when you reboot, so it |
| 23 |
should be forgotten about on a reboot. |
| 24 |
|
| 25 |
William |
| 26 |
|
| 27 |
[1] http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES |
Archives