parse.y: document quoting rules

2012-04-21 Thread Jason McIntyre
it seems that we have lots of config files that currently have no guidelines as to what needs quoting, and what does not. the diff below is for pf.conf.5, and attempts to clarify that. if no one disagrees, i'll do it for all those that use parse.y. that is: /usr/src/sbin/iked/parse.y

The rivolution web

2012-04-21 Thread newusers
Hello, I'm Bybor, your new social network! Get to know me on, www.bybor.com [demime 1.01d removed an attachment of type image/jpeg which had a name of bybor LOGO.jpg] April 27, 2012

Re: parse.y: document quoting rules

2012-04-21 Thread Florian Obser
On 04/21/12 19:33, Jason McIntyre wrote: any dissention, or inaccuracies? jmc Index: pf.conf.5 === RCS file: /cvs/src/share/man/man5/pf.conf.5,v retrieving revision 1.513 diff -u -r1.513 pf.conf.5 --- pf.conf.5 31 Jan

Re: parse.y: document quoting rules

2012-04-21 Thread Florian Obser
On 04/21/12 20:45, Florian Obser wrote: I think it should apply to the whole grammar: This does not work (syntax error) pass in tag tag pass in tag /foo while this works: pass in tag tag pass in tag /foo Of course these rules combined are nonsense. What I meant to say: I

Re: parse.y: document quoting rules

2012-04-21 Thread Jason McIntyre
On Sat, Apr 21, 2012 at 08:45:25PM +0200, Florian Obser wrote: Keywords need to be quoted, too. This does not work (syntax error) include tag while this works: include tag What got me thinking about this: Is that sentence supposed to describe quoting rules for the include

sys_pipe: take fd table lock after allocating memory

2012-04-21 Thread Mike Belopuhov
there's no apparent need to take a file descriptor table lock before we've done allocating pipe structures and buffers. ok? Index: sys/kern/sys_pipe.c === RCS file: /home/cvs/src/sys/kern/sys_pipe.c,v retrieving revision 1.61 diff -u