Re: /var/lock

2011-01-05 Thread haad
On Mon, Jan 3, 2011 at 1:21 PM, Alan Barrett a...@cequrux.com wrote: On Mon, 03 Jan 2011, rud...@eq.cz wrote: Adam Hamsik wrote: Modified Files:     src/distrib/sets/lists/base: mi     src/etc/mtree: NetBSD.dist.base Log Message: Add /var/lock directory to base set it's used by LVM

Re: /var/lock

2011-01-05 Thread David Holland
On Wed, Jan 05, 2011 at 02:09:16AM +0300, Valeriy E. Ushakov wrote: 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

Re: /var/lock

2011-01-04 Thread Valeriy E. Ushakov
On Tue, Jan 04, 2011 at 05:23:08 +, David Holland wrote: On Tue, Jan 04, 2011 at 02:58:18AM +0100, Adam Hamsik wrote: Are they really *lock* files? It's lvm subsystem lock file. Does it need to be specific in any way ? If it's really a lock file that may need to persist across

Re: /var/lock

2011-01-04 Thread David Holland
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

Re: /var/lock

2011-01-04 Thread Adam Hamsik
On Jan,Tuesday 4 2011, at 8:56 AM, Alan Barrett wrote: On Tue, 04 Jan 2011, Adam Hamsik wrote: I would like to have something persistent between reboots. I have found that we already have /var/spool/lock. Therefore /var/spool/lock/lvm/ seems to be might preferred place. Do you agree ? I

Re: /var/lock

2011-01-04 Thread Valeriy E. Ushakov
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 gross. RHEL5 I have at work has /var

Re: /var/lock

2011-01-04 Thread Valeriy E. Ushakov
On Tue, Jan 04, 2011 at 23:41:00 +0100, Adam Hamsik wrote: Subject: Re: /var/lock From: Adam Hamsik haa...@gmail.com Date: Tue, 4 Jan 2011 23:41:00 +0100 Cc: source-changes-d@NetBSD.org To: Alan Barrett a...@cequrux.com On Jan,Tuesday 4 2011, at 8:56 AM, Alan Barrett wrote: On Tue

Re: /var/lock

2011-01-04 Thread Valeriy E. Ushakov
On Wed, Jan 05, 2011 at 00:43:11 +0100, Adam Hamsik wrote: On Jan,Wednesday 5 2011, at 12:13 AM, Valeriy E. Ushakov wrote: On Tue, Jan 04, 2011 at 23:41:00 +0100, Adam Hamsik wrote: Ok I will change it to /var/spool/lock/lvm tomorrow and I will update hier to mention those

/var/lock

2011-01-03 Thread Alan Barrett
On Mon, 03 Jan 2011, rud...@eq.cz wrote: Adam Hamsik wrote: Modified Files: src/distrib/sets/lists/base: mi src/etc/mtree: NetBSD.dist.base Log Message: Add /var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking

Re: /var/lock

2011-01-03 Thread Adam Hamsik
On Jan,Monday 3 2011, at 1:21 PM, Alan Barrett wrote: On Mon, 03 Jan 2011, rud...@eq.cz wrote: Adam Hamsik wrote: Modified Files: src/distrib/sets/lists/base: mi src/etc/mtree: NetBSD.dist.base Log Message: Add /var/lock directory to base set it's used by LVM and other tools

Re: /var/lock

2011-01-03 Thread Bernd Ernesti
/var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking for him. Why is /var/run not the right place for your needs? Also, where was this discussed? If it was discussed, please update hier(7) according to the outcome

Re: /var/lock

2011-01-03 Thread Adam Hamsik
/etc/mtree: NetBSD.dist.base Log Message: Add /var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking for him. Why is /var/run not the right place for your needs? Also, where was this discussed? If it was discussed, please

Re: /var/lock

2011-01-03 Thread Alan Barrett
On Mon, 03 Jan 2011, Adam Hamsik wrote: Log Message: Add /var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking for him. Why is /var/run not the right place for your needs? Also, where was this discussed

Re: /var/lock

2011-01-03 Thread Adam Hamsik
On Jan,Monday 3 2011, at 4:08 PM, Alan Barrett wrote: On Mon, 03 Jan 2011, Adam Hamsik wrote: Log Message: Add /var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking for him. Why is /var/run not the right place for your needs

Re: /var/lock

2011-01-03 Thread Takahiro Kambe
Hi, In message c5724e4b-3267-40d5-a93a-425072bb2...@gmail.com on Tue, 4 Jan 2011 02:46:17 +0100, Adam Hamsik haa...@gmail.com wrote: I would like to have something persistent between reboots. I have found that we already have /var/spool/lock. Therefore /var/spool/lock/lvm/

Re: /var/lock

2011-01-03 Thread Adam Hamsik
/lvm for them unless those files are temporary files like printer outputs. So we have these options: 1) /var/lock/lvm - needs much more discussion 2) /var/spool/lock/lvm 3) /var/run/lvm - not persistent, it needs to be recreated every time 4) /var/db/lvm What would you prefer ? Regards Adam.

Re: /var/lock

2011-01-03 Thread Matt Thomas
On Jan 3, 2011, at 5:58 PM, Adam Hamsik wrote: On Jan,Tuesday 4 2011, at 2:51 AM, Takahiro Kambe wrote: So we have these options: 1) /var/lock/lvm - needs much more discussion 2) /var/spool/lock/lvm 3) /var/run/lvm - not persistent, it needs to be recreated every time 4) /var/db/lvm

Re: /var/lock

2011-01-03 Thread David Holland
On Tue, Jan 04, 2011 at 02:58:18AM +0100, Adam Hamsik wrote: Are they really *lock* files? It's lvm subsystem lock file. Does it need to be specific in any way ? If it's really a lock file that may need to persist across reboots, then 2) /var/spool/lock/lvm is the right place. --