Hi.

I configured some processes such as the subversion sever process (svnserve) to be executed by inetd. Inetd, when configured with nowait option, is documented to fork() and exec() the server process on every request. By the way, documentation states that process and task controls are inherited across fork() system call so that, even if an user svnuser and a default user project user.svnuser has been setup, the svnserve instance is not being executed in the user.svnuser project. The consequence is that, for example, project.cpu-cap options for that process does not take effect.

Is there a way to enforce this kind of behavior? Maybe I could find a way to execute a server process another way: in the case of svnserve I could execute it in daemon mode and not via inet. Documentation is clear about fork(), but it seems odd to me that in the case of inet server processes the project database is being ignored, while it is not in the case of at and cron.

Do you have any hint about this?

hey there,

perhaps the easiest thing to do would be to wrap the svn process. That way you could let inetd fork and exec your wrapper, which could set the project and project variables before running your svn session.

Just a thought. I'm not sure how else (without affecting the entire system) you could enforce the correct project settings if the inetd server is forking/execing and (as always) running as root.

Best wishes,

Mike