[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On Tue, Jan 04, 2011 at 19:43:49 +0000, David Holland wrote:
> On Tue, Jan 04, 2011 at 11:46:34AM +0300, Valeriy E. Ushakov wrote:
> > > > 2) /var/spool/lock/lvm
> > >
> > > is the right place.
> > Ugh. What does it have to do with spooling?
> What do any locks have to do with spooling? Historically, /var/spool
> is for "stuff". Since then lots of things traditionally in /var/spool
> have been moved into /var, like /var/cron, /var/at, /var/rwho, and so
> forth, mostly for no clear reason but I guess because they don't have
> anything to do with "spooling", whatever that means.
> Anyway, the reason this whole thread started out with /var/lock is
> that the Linux world apparently also did this with /var/spool/lock.
But our /var/spool/lock is specifically uucp's lockdir (uucp/daemon).
Creating lvm subdir beneath is (owned by operator) feels monumentally
RHEL5 I have at work has /var/lock, with /var/lock/uucp being
equivalent of our /var/spool/lock.
Main Index |
Thread Index |