[[!meta copyright="Copyright © 2008, 2009, 2010, 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_hurd]] There have been several discussions and proposals already, about adding a suitable logging mechanism to translators, for example. Decide / implement / fix that (all?) running (passive?) translators' output should show up on the (Mach / Hurd) console / syslog. [[!taglink open_issue_documentation]]: [[!message-id "87oepj1wql.fsf@becket.becket.net"]] [[!taglink open_issue_documentation]]: Neal once had written an email on this topic. IRC, freenode, #hurd, 2011-11-06 about CLI_DEBUG, you can use #define CLI_DEBUG(fmt, ...) { fprintf(stderr, fmt, ## __VA_ARGS__); fflush(stderr); } Isn't stderr in auto-flush mode by default? man setbuf: The standard error stream stderr is always unbuffered by default. tschwinge: "by default" is the important thing here in the case of translators iirc stderr is buffered youpi: Oh! That sounds wrong. IRC, freenode, #hurd, 2011-11-23 we'd need a special logging task for hurd servers if syslog would work, that could be used optionally no, it relies on services provided by the hurd i'm thinking of something using merely the mach interface e.g. using mach_msg to send log messages to a special port used to reference the logging service which would then store the messages in a circular buffer in ram maybe sending to syslog if the service is available the hurd system buffer if you want