On Mon, Nov 18, 2019 at 07:57:09PM -0700, Theo de Raadt wrote: > Florian Obser <[email protected]> wrote: > > > On Tue, Nov 19, 2019 at 12:15:34AM +0100, Klemens Nanni wrote: > > > On Mon, Nov 18, 2019 at 10:19:47PM +0100, Klemens Nanni wrote: > > > > With that, my initial case is no longer misleading; alternatively, I > > > > can implement the dash semantic, but that's another diff. > > > Hm, that makes the default setup (no /etc/unwind.conf, empty > > > unwind_flags) always print a warning, which is ugly. > > > > It's not just ugly, it's missleading. We want unwind to be the best it > > can be *without* a config file. We don't to suggest a config file. We > > want to steer people away from pushing buttons, not towards. > > Agree strongly. > > > Btw. I'm not sure the parser can work with stdin, I think it needs to > > seek, which you can't do on stdin? But I might be mistaken on multiple > > levels. > > No, I think it only does ungetc and (nested fd's in case of include > if you do that)
If it is the normal parse.y setup then it does work on stdin (at least for simple configs). I do use stdin with bgpd to validate rpki files before putting them into place. -- :wq Claudio
