Colin, I'm content with the daemon(3) function; I had overlooked it because I was looking for the 'usual sequence' of calls as laid out in Advanced Programming in the Unix Environment: - umask() - chdir() - closing unneeded filedescriptors - ensuring 0, 1, 2 are open to something that makes sense, /dev/null for example - fork() - parent exit() - setsid() - optionally another fork()
The order of the umask(), chdir(), close(), calls doesn't matter much, and the specific arguments don't necessarily matter much, different programs will make different choices and it's usually fine if the author thought about it. Using daemon(3) is fine, but since it is isn't standardized, I'm not accustomed to seeing it, hence my mistake this time. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279388 Title: [MIR] thermald To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1279388/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
