I don't know of any security issues that would arise from this behaviour but that doesn't mean there aren't any.
I was wondering why tmda-ofmipd was doing this in the first place. It has a nasty side effect when started with supervise from the daemontools package. I found if I manually killed the hung root process, it immediately set up some kind of loop where copies of tmda-ofmipd were spawned out of control. I had to quickly stop the supervise process before my machine ran out of resources. Maybe it's just me, but I don't like long running root processes on my box that aren't supposed to be there. I did a bit of hacking on tmda-ofmipd and added an extra option to daemonize the process. With this option, I don't need to use an '&' at the end of the command line to force tmda-ofmipd into the background. Best of all, with this option init scripts behave themselves producing only one process running under the proper user. It works when used with the -u option and when the program if invoked using su as in: su - <username> -c tmda-ofmipd -D <more options> -D is the option I use to daemonize the process. If this is something people feel might be generally useful, I'll submit a patch of the changes I've made. Any comments from the TMDA developers? Jason? Andrew Malcolm wrote: > I have the same problem. One extra root init process running. I guess > it's not really a big deal is it? Other than wasting resources. There's > no security issues right? > > Malcolm _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
