Hi, We (Knorrie, andi, and me) realized, that birdc outputs server errors to stdout much like normal server output. When scripting birdc, it can be helpful to have those on stderr instead. Simple use case: birdc CMD >/dev/null If everything is fine, no output at all. If something goes wrong, output! There are a few aspects: 1. Is this useful? Hopefully. If you think this is a studpid idea, pleas explain! 2. Should this be the default (in an upcoming version)? I don't know, how many non humans depend on *all* output going to stdout and neglect stderr? Ignoring stderr IMHO is a design flaw. But well, this is a question of backward compatibility. NOTE: Something should be added to the ChangeLog, so people are not too surprised. 3. If the answer to (2) is "Need backward compatibility": Do we need some --enable-stderr then? Cheers Christian -- www.cosmokey.com