namespace {
/* Purposely *not* derived from std::exception */
- struct DaemonExitException {
+ struct DaemonExitException {
DaemonExitException(unsigned c) : code(c) {}
unsigned code;
};
std::string::size_type komma (arg.find(','));
if (komma == std::string::npos) {
boost::trim(arg);
- consoleLog(arg);
+ if (arg == std::string("none")) consoleLog("");
+ else if (!arg.empty()) consoleLog(arg);
} else {
std::string arg1 (arg,0,komma);
std::string arg2 (arg,komma+1);
// here after setting default parameters
senf::Daemon::configure();
}
-
+
void init() {
// Initialize application. Setup all necessary objects. After init()
// has completed, the startup should not fail
Since there are times, where separating init() and run() into two separate functions is
difficult, instead of defining init() and run(), the member main() may be defined. This member
must call detach() as soon as initialization is completed to detach from the foreground
- terminal.
+ terminal.
+ \code
+ class MyDaemon : public senf::Daemon
+ {
+ // 'configure()' like above. Don't implement 'init()' or 'run()' if you implement 'main()'.
+
+ void main() {
+ // Initialize application. Setup all necessary objects. When implementing main(), the
+ // objects will most often live on the stack.
+
+ MyAppObject app;
+
+ if (some_error)
+ // Call Daemon::exit() to terminate execution prematurely
+ exit(1);
+
+ // After initialization is complete, you *must* call 'detach()'.
+
+ detach()
+
+ // Now we can start the application main loop
+
+ app.run();
+ }
+ };
+ \endcode
\see
\ref senf::Daemon class \n