[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnserve could save its PID somewhere

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-06-20 10:29:00 CEST

Grzegorz B. Prokopski wrote:

>Hi,
>
>Before filling in a wishlist bug, I am supposed to discuss it here
>(according to "Issue Tracker Guidelines"), so here it goes.
>
>I am in process of setting up different services in chroots
>without /proc. This works just fine for pretty much all services as
>most of daemons leave their "main deamon PID" in some .pid file,
>usually in /var/run/$name.pid or /var/run/$name/$name.pid.
>The PID is necessary to send a signal to daemon when we want it
>to finish execution (and shut down nicely) [*]
>
>For anonymous access to our repositories I wanted to setup
>svnserve in a similar way. But apparently svnserve has no option
>to create the .pid file. Therefore I wanted to ask you whether
>it could be added, so that something of that shape worked:
>
> $ svnserve -d -p /var/run/svnserve/svnserve.pid
>
>
Of course this coule be added. It should be quite simple, too. Care to
write a patch?

>[*] Btw: what signal should I send to svnserve to let it know
>that I want it to shut down? Is simple TERM (15) the way to go?
>
Come to think of it, svnserve doesn't handle signals as well as it
should -- it should use some of the logic from the client, or svnlook.
Once that's done, SIGTERM should be just fine.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 20 10:29:23 2004

This is an archived mail posted to the Subversion Dev mailing list.