On Thu, Jul 22, 2010 at 08:05:55PM -0600, Theo de Raadt wrote: > > i went on and tested '-nvf ./cow.conf' in each of: > > bgpd, ldapd, ldpd, ospfd, relayd, ripd, snmpd, smtpd, ypldap. > > they all errored out only exactly on lines 4 and 6 > > > > m4(1) seems to parse the file fine though. > > > > assuming these are all supposed to be consistent, > > is pfctl/m4 the way things should be, or are all these other > > things the way things should be? > > there may be consistancy problem's between our daemons, but our > daemons ARE NOT M4. What next?
i checked m4 because i recall seeing reference to 'much like cpp(1) or m4(1), macros can be used...' comment i've seen in one or more of the manpages. > sh doesn't parse them! Oh my god, mozilla hates them. i didn't know if the above i tested are meant to be built around the same parse.y model/framework, but i see the parse.y/yylex stuff in their source dirs, so that was the original nature of my question -- by virtue of ipsecctl parsing it fine in a previous version, but not in -current, is this specific behaviour the way of the future or accidental? -- jared
