Bump!
On Sun, 13 Jun 2010 12:34:55 +0100, Stuart Henderson wrote:
>On 2010/06/13 21:01, Rod Whitworth wrote:
>> On Sun, 13 Jun 2010 10:48:49 +0100, Stuart Henderson wrote:
>>
>> >On 2010/06/13 17:31, Rod Whitworth wrote:
>> >> On Sun, 13 Jun 2010 07:44:26 +0100, Jason McIntyre wrote:
>> >>
>> >
Top Shop
Navijaj uz 10% POPUSTA samo do 11. jula!
Pripremi se za sledeDu tekmu!
UE>ivaj uz Air Sofa Bed: pravo rešenje za vatreno navijanje uz uštedu!
Samo za registrovane D
lanove tokom fudbalskog Prvenstva popust 10%
Klikni i naruD
i odmah!
Ponuda vaE>i samo do 11. jula
Quelle
A dok muÅ
GMINSTAL Realizamos trabajos de:
* Plomeria
* Gas
* Calefaccisn
* Reparaciones de humedades
* Filtraciones
* Reformas
* Obras nuevas
* Tramitaciones en METROGAS - GAS NATURAL BAN
* Colocacisn de artefactos
* Mesadas
* Cocinas
* Artefactos de baqo
* Hidromasaje
I should have been more specific. This is not a vote as to where we
should put the default.
If you think of the constraints (usually not NFS, user-writable), there
are about two locations that make sense: /tmp or /var/tmp.
Also remember that it makes no sense for those locks to survive reboot.
So
On Wed, 16 Jun 2010, J.C. Roberts wrote:
> Stuffing the LOCKDIR under pobj (where ever you keep pobj) seems to
> make more sense and requires fewer changes.
Some have obj on nfs.
--
Antoine
On Wed, 16 Jun 2010 13:38:12 +0200 Marc Espie wrote:
>
> Historically, I did leave LOCKDIR empty in bsd.port.mk.
> Now, I'm wondering if I should define it to something such as
> /tmp/portslocks ?
>
> My assumption was that it would be difficult to be certain that
> dotlocks could be created anyw
ous scenarios.
This whole block was added in r1.28 when bridge(4) was added.
> Updated patch at
> http://patrick.ld.net.au/20100616-fix-gratuitous-reset-nopromisc.patch.
> I've also created bug 6404/kernel.
>
> Cheers,
>
> Patrick
>
> --
> http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting
On Wed, Jun 16, 2010 at 02:15:37PM +0200, Marc Espie wrote:
> On Wed, Jun 16, 2010 at 02:11:47PM +0200, Bret S. Lambert wrote:
> > On Wed, Jun 16, 2010 at 02:02:37PM +0200, Antoine Jacoutot wrote:
> > > On Wed, 16 Jun 2010, Marc Espie wrote:
> > > > > 3 days is a bit short on some arch. /var/tmp gi
On 2010/06/16 14:00, Marc Espie wrote:
> On Wed, Jun 16, 2010 at 12:51:20PM +0100, Stuart Henderson wrote:
> > On 2010/06/16 13:45, Antoine Jacoutot wrote:
> > > On Wed, 16 Jun 2010, Marc Espie wrote:
> > >
> > > > Historically, I did leave LOCKDIR empty in bsd.port.mk.
> > > > Now, I'm wondering
ng it in.
>> + * Has been set to the trunk interface. ifp_orig preserves
the physical
>
> it's not mentioned explicitly in style(9) but wrapping to
> 80 columns is preferred.
Updated patch at
http://patrick.ld.net.au/20100616-fix-gratuitous-reset-nopromisc.patch.
I've also created bug 6404/kernel.
Cheers,
Patrick
--
http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting
On Wed, Jun 16, 2010 at 02:11:47PM +0200, Bret S. Lambert wrote:
> On Wed, Jun 16, 2010 at 02:02:37PM +0200, Antoine Jacoutot wrote:
> > On Wed, 16 Jun 2010, Marc Espie wrote:
> > > > 3 days is a bit short on some arch. /var/tmp gives you 7 days,
> > > > but isn't cleared at boot...
> > > >
> > >
On Wed, Jun 16, 2010 at 02:02:37PM +0200, Antoine Jacoutot wrote:
> On Wed, 16 Jun 2010, Marc Espie wrote:
> > > 3 days is a bit short on some arch. /var/tmp gives you 7 days,
> > > but isn't cleared at boot...
> > >
> > daily could be set to ignore those... after all, it already ignores some
> >
On Wed, 16 Jun 2010, Marc Espie wrote:
> > 3 days is a bit short on some arch. /var/tmp gives you 7 days,
> > but isn't cleared at boot...
> >
> daily could be set to ignore those... after all, it already ignores some other
> stuff.
Sure, I was just pointing that one needed to be careful ;-)
--
On Wed, Jun 16, 2010 at 12:51:20PM +0100, Stuart Henderson wrote:
> On 2010/06/16 13:45, Antoine Jacoutot wrote:
> > On Wed, 16 Jun 2010, Marc Espie wrote:
> >
> > > Historically, I did leave LOCKDIR empty in bsd.port.mk.
> > > Now, I'm wondering if I should define it to something such as
> > > /t
On Wed, Jun 16, 2010 at 01:45:30PM +0200, Antoine Jacoutot wrote:
> On Wed, 16 Jun 2010, Marc Espie wrote:
>
> > Historically, I did leave LOCKDIR empty in bsd.port.mk.
> > Now, I'm wondering if I should define it to something such as
> > /tmp/portslocks ?
> >
> > My assumption was that it would
On 2010/06/16 13:45, Antoine Jacoutot wrote:
> On Wed, 16 Jun 2010, Marc Espie wrote:
>
> > Historically, I did leave LOCKDIR empty in bsd.port.mk.
> > Now, I'm wondering if I should define it to something such as
> > /tmp/portslocks ?
> >
> > My assumption was that it would be difficult to be ce
On 2010/06/16 18:36, Patrick Coleman wrote:
> /*
>* If packet is unicast and we're in promiscuous mode, make sure it
>* is for us. Drop otherwise.
> + *
> + * Check ifp and ifp_orig, to catch promiscuous members of a
> + * non-promiscuous trunk.
>*/
>
On Wed, 16 Jun 2010, Marc Espie wrote:
> Historically, I did leave LOCKDIR empty in bsd.port.mk.
> Now, I'm wondering if I should define it to something such as
> /tmp/portslocks ?
>
> My assumption was that it would be difficult to be certain that dotlocks could
> be created anywhere. But it se
Historically, I did leave LOCKDIR empty in bsd.port.mk.
Now, I'm wondering if I should define it to something such as
/tmp/portslocks ?
My assumption was that it would be difficult to be certain that dotlocks could
be created anywhere. But it seems that most machines have local /tmp/ these
days.
6000, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val
844767321 ecr 0,sackOK,eol], length 0
11:41:39.411987 00:04:23:c9:bd:d0 > 00:25:00:a0:2a:6e, ethertype IPv4
(0x0800), length 60: 10.10.50.2. > 10.10.50.1.51744: Flags [R.], seq 0,
ack 2093396001, win 0, length 0
[2] Also up
20 matches
Mail list logo
