It may be useful to use more specific error codes, such as EX_OSERR for a failed fork() call.

In addition, your output statement can be improved. Since fork() updates ERRNO on failure, replace your error output with just a call to std::perror() for a more accurate one.

Here's what all this would look like with these changes:

 if (pid < 0) { std::perror("fork"); return EX_OSERR; } 

Many of your member functions don't modify data members, yet they don't have const. This helps to prevent accidental modification of data members (causing a compiler error) while revealing more of the function's intent to others.

Here's an example using one of your member functions:

 std::string path(void) const; 

 std::string LoggerConfig::path(void) const { return get(LoggerConfig::LogPath) + "/" + get(LoggerConfig::LogName); } 

Another note: Unlike in C, it's unnecessary to specify void for functions that don't take any arguments in C++. The compiler will already be aware of this.

In parseOpts(), it doesn't look like you should try to catch either an std::exception or ... and then throw either one as an std::runtime_error. The specific exception you may be looking for is std::logic_error. But this would depend on exactly which exception(s) can be thrown in this function.

In showHelp(), you don't need to do all that flushing with std::endl, which affects performance. Instead, output a "\n" for just a newline.

Since you're using C++11, you can use range-based for loops.

For example, this can be applied to the loop in dump():

 for (auto& it : configMap) { std::cout << it.first << "=" << it.second << std::endl; } 

It may be useful to use more specific error codes, such as EX_OSERR for a failed fork() call.

In addition, your output statement can be improved. Since fork() updates errno on failure, replace your error output with just a call to std::perror() for a more accurate one.

 if (pid < 0) { std::perror("fork"); return EX_OSERR; } 

When passing a non-native type (such as std::string) to a function, it's preferred to pass by const& to avoid an extra copy:

 bool contains(std::string const& argName); 

 bool CommandLineOpts::contains(std::string const& argName) { return commandLineMap.count(argName); } 

Also regarding const: many of your member functions don't modify data members, yet they don't have const. This helps to prevent accidental modification of data members (causing a compiler error) while revealing more of the function's intent to others.

 std::string path(void) const; 

 std::string LoggerConfig::path(void) const { return get(LoggerConfig::LogPath) + "/" + get(LoggerConfig::LogName); } 

Unlike in C, it's unnecessary to specify void for functions that take no arguments. The compiler will already be aware of this.

In parseOpts(), it doesn't look like you should try to catch either an std::exception or ... and then throw either one as an std::runtime_error. The specific exception you may be looking for is std::logic_error. But this would depend on exactly which exception(s) can be thrown in this function.

In showHelp(), you don't need to do all that flushing with std::endl, which affects performance. Instead, output a "\n" for just a newline.

Since you're using C++11, you can use range-based for loops. For example, this can be applied to the loop in dump():

 for (auto& it : configMap) { std::cout << it.first << "=" << it.second << std::endl; } 

It may be useful to use more specific error codes, such as EX_OSERR for a failed fork() call.

In addition, your output statement can be improved. Since fork() updates ERRNO on failure, replace your error output with just a call to std::perror() for a more accurate one.

Here's what all this would look like with these changes:

 if (pid < 0) { std::perror("fork"); return EX_OSERR; } 

Many of your member functions don't modify data members, yet they don't have const. This helps to prevent accidental modification of data members while revealing more of the function's intent to others.

Here's an example using one of your member functions:

 std::string path(void) const; 

 std::string LoggerConfig::path(void) const { return get(LoggerConfig::LogPath) + "/" + get(LoggerConfig::LogName); } 

Another note: Unlike in C, it's unnecessary to specify void for functions that don't take any arguments in C++.

in parseOpts(), it doesn't look like you should try to catch either an std::exception or ... and then throw either one as an std::runtime_error. The specific exception you may be looking for is std::logic_error. But this would depend on exactly which exceptions can be thrown in this function.

In showHelp(), you don't need to do all that flushing with std::endl. Instead, output a "\n" for just a newline.

Since you're using C++11, you can use range-based for loops.

For example, this can be applied to the loop in dump():

 for (auto& it : configMap) { std::cout << it.first << "=" << it.second << std::endl; } 

It may be useful to use more specific error codes, such as EX_OSERR for a failed fork() call.

In addition, your output statement can be improved. Since fork() updates ERRNO on failure, replace your error output with just a call to std::perror() for a more accurate one.

Here's what all this would look like with these changes:

 if (pid < 0) { std::perror("fork"); return EX_OSERR; } 

Many of your member functions don't modify data members, yet they don't have const. This helps to prevent accidental modification of data members (causing a compiler error) while revealing more of the function's intent to others.

Here's an example using one of your member functions:

 std::string path(void) const; 

 std::string LoggerConfig::path(void) const { return get(LoggerConfig::LogPath) + "/" + get(LoggerConfig::LogName); } 

Another note: Unlike in C, it's unnecessary to specify void for functions that don't take any arguments in C++. The compiler will already be aware of this.

In parseOpts(), it doesn't look like you should try to catch either an std::exception or ... and then throw either one as an std::runtime_error. The specific exception you may be looking for is std::logic_error. But this would depend on exactly which exception(s) can be thrown in this function.

In showHelp(), you don't need to do all that flushing with std::endl, which affects performance. Instead, output a "\n" for just a newline.

Since you're using C++11, you can use range-based for loops.

For example, this can be applied to the loop in dump():

 for (auto& it : configMap) { std::cout << it.first << "=" << it.second << std::endl; }