#2535 Clients shouldn't cause log messages

sfcb (1090)

Clients compiled against the sfcb code often cause syslog entries to be created. This is because the clients are using the same libraries that the sfcbd uses. The libraries should be able to determine when they are being called from a client, and not generate syslogs in that case.


  • Michael Chase-Salerno

    The attached patch adds a global variable to mlog that controls the calling of syslog and the printing to the console. It is set in sfcbd to enable those functions when called from the daemon, but will typically not be set by a client program.

  • Michael Chase-Salerno

    committed to CVS HEAD and git master

  • Michael Chase-Salerno

    Added a global variable which is set in the sfcbd process. This variable will enable logging only when set, so clients will typically not set it and therefore not generate syslog entries.

  • Michael Chase-Salerno

    • status: open --> pending-fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks