I think I understand what's happening, though I'm not sure that it should...
After the daemon's double-fork (with setsid()), the utility of the group
identification seems lost.
With a bit more detail:
Say I have a directory owned by user "user1", who is a member of
"group1"; and that "us
I have a peculiar problem with a daemon. Some of the tasks that the daemon
needs to accomplish should be done with reduced priviledges, particularly
if they are complex or depend on user input. So the daemon forks a child
process, which setuid's to some lesser user.
Unfortunately, as soon as th
2 matches
Mail list logo