Re: /var/lock

2011-01-03 Thread Alan Barrett
On Tue, 04 Jan 2011, Adam Hamsik wrote: > > Are they really *lock* files? > > It's lvm subsystem lock file. Does it need to be specific in any way ? Does it need to persist across reboot? > So we have these options: > > 1) /var/lock/lvm -> needs much more discussion > 2) /var/spool/lock/lvm >

Re: CVS commit: src/sys/dev/acpi

2011-01-03 Thread Jukka Ruohonen
On Tue, Jan 04, 2011 at 05:48:49AM +, Jukka Ruohonen wrote: > "Do not queue functions via sysmon_taskq(9) in the pmf(9) resume hooks. >There is a small and unlikely race when the drivers are loaded as modules; >suspend, resume, queue a function, and immediately unload the module." An

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. -

Re: CVS commit: src

2011-01-03 Thread David Holland
On Sun, Jan 02, 2011 at 12:58:13PM +0200, Antti Kantee wrote: > > Add an INRELOOKUP namei flag. Sigh. (We don't need more namei flags.) > > > > However, because of a protocol deficiency puffs relies on being able > > to keep track of VOP_LOOKUP calls by inspecting their contents, and > > this

Re: CVS commit: src/sys/uvm

2011-01-03 Thread Masao Uebayashi
I take silence as "no objection". On Thu, Dec 23, 2010 at 12:48:04PM +0900, Masao Uebayashi wrote: > On Wed, Dec 22, 2010 at 05:37:57AM +, YAMAMOTO Takashi wrote: > > hi, > > > > > Could you ack this discussion? > > > > sorry for dropping a ball. > > > > > > > > On Tue, Dec 07, 2010 at 01:

Re: /var/lock

2011-01-03 Thread Takahiro Kambe
In message on Tue, 4 Jan 2011 02:58:18 +0100, Adam Hamsik wrote: >> Are they really *lock* files? > > It's lvm subsystem lock file. Does it need to be specific in any way ? I want to know just life time of the lock file(s), including the file is single one or multiple one. When

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

Re: /var/lock

2011-01-03 Thread Adam Hamsik
On Jan,Tuesday 4 2011, at 2:51 AM, Takahiro Kambe wrote: > Hi, > > In message > on Tue, 4 Jan 2011 02:46:17 +0100, > 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

Re: /var/lock

2011-01-03 Thread Takahiro Kambe
Hi, In message on Tue, 4 Jan 2011 02:46:17 +0100, 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 ? Also /var/sp

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 rig

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 dis

Re: /var/lock

2011-01-03 Thread Adam Hamsik
On Jan,Monday 3 2011, at 2:54 PM, Bernd Ernesti wrote: > On Mon, Jan 03, 2011 at 02:46:31PM +0100, Adam Hamsik wrote: >> >> 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/set

Re: /var/lock

2011-01-03 Thread Bernd Ernesti
On Mon, Jan 03, 2011 at 02:46:31PM +0100, Adam Hamsik wrote: > > 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 > >>>

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

/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 L

Re: CVS commit: src/tests/fs/common

2011-01-03 Thread Manuel Bouyer
On Fri, Dec 31, 2010 at 07:45:26PM +, David Laight wrote: > [...] > >From what I remember of the NFS protocol, the following 'rules' applied: > 1) If you export part of a filesystem, you export all of the filesystem. that's probably trye > 2) If you give anyone access, you give everyone acces

Re: CVS commit: src

2011-01-03 Thread rud...@eq.cz
Adam Hamsik wrote: Module Name:src Committed By: haad Date: Sat Jan 1 12:49:49 UTC 2011 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 grou