views:

1341

answers:

3

Hi!

I'm planning to package OpenTibia Server for Debian. One of the things I want to do is add startup via /etc/init.d and daemonization of the otserv process.

Thing is, we should probably redirect output to syslog. This is usually done via the syslog() function. Currently, the code is swarmed with:

std::cout << "Stuff to printout" << std::endl;

Is there a proper, easy to add, way to redirect standard output and standard error output into syslog without replacing every single "call" to std::cout and friends?

+1  A: 

Try wrapping the execution of the binary with a suitable script, that just reads stdout and stderr, and send any data read from them on using syslog(). That should work without any code changes in the wrapped application, and be pretty easy.

Not sure if there are existing scripts to pipe into, but writing one shouldn't be hard if not.

unwind
+6  A: 

You can pipe your stdout to syslog with the logger command:

NAME

 logger - a shell command interface to the syslog(3) system log module

SYNOPSIS

 logger [-isd] [-f file] [-p pri] [-t tag] [-u socket] [message ...]

DESCRIPTION

 Logger makes entries in the system log.  It provides a shell command
 interface to the syslog(3) system log module.

If you don't supply a message on the command line it reads stdin

Alnitak
+3  A: 

You can redirect any stream in C++ via the rdbuf() command. This is a bit convoluted to implement but not that hard.

You need to write a streambuf that would output to syslog on overflow(), and replace the std::cout rdbuf with your streambuf.

An example, that would output to a file (no error handling, untested code)

#include <iostream>
#include <fstream>
using namespace std;

int main (int argc, char** argv) {
   streambuf * yourStreamBuffer = NULL;
   ofstream outputFileStream;
   outputFileStream.open ("theOutputFile.txt");

   yourStreamBuffer = outputFileStream.rdbuf();
   cout.rdbuf(yourStreamBuffer);

   cout << "Ends up in the file, not std::cout!";

   outputFileStream.close();

   return 0;
 }
Pieter
Almost what I was looking for, however, "logger" supplies me extra information, especially if I simply produce a wrapper bash script. However, thanks for the information, and I'm so sorry I cannot mark both answers as The Answers(tm).
Ivan Vučica