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.
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
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 for him.
> >>
>
>>>>> 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
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 th
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 LV
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
ould be /var/db/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.
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 recrea
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
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.
-
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 discuss
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 persis
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 had forgotten about /var/spool/lock; it's been a long time
tuff". 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
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 ?
ecause 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 lock
On Tue, Jan 04, 2011 at 23:41:00 +0100, Adam Hamsik wrote:
> Subject: Re: /var/lock
> From: Adam Hamsik
> Date: Tue, 4 Jan 2011 23:41:00 +0100
> Cc: source-changes-d@NetBSD.org
> To: Alan Barrett
>
>
> On Jan,Tuesday 4 2011, at 8:56 AM, Alan Barrett wrote:
>
&g
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:
>> Subject: Re: /var/lock
>> From: Adam Hamsik
>> Date: Tue, 4 Jan 2011 23:41:00 +0100
>> Cc: source-changes-d@NetBSD.org
>> To: Alan Bar
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
On Mon, Jan 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:
&g
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'
22 matches
Mail list logo
