Bug#385308: [Pkg-xen-devel] Bug#385308: Please provide way to run xend in the foreground, without daemonizing
On Wed, Aug 30, 2006 at 03:08:21PM +0200, Bastian Blank wrote: On Wed, Aug 30, 2006 at 02:21:07PM +0200, Andras Korn wrote: it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). They are started by xend, so please provide concret informations. OK, they don't work when not started by xend: xend can't connect to the xenstored socket, which is strange because unixclient can. I guess xend removes and recreates the socket even if xenstored is running, or something like that. I'm now back to running xenconsoled and xenstored from xend, but xenconsoled sometimes fails (apparently when a domU crashes and is restarted before its console can be attached to), and is not restarted by xend. It would really be a lot nicer to have them supervised by runit separately, so that if any of them were to fail, they could be restarted automatically. Andras -- Andras Korn korn at chardonnay.math.bme.hu http://chardonnay.math.bme.hu/~korn/ QOTD: Money can't buy friends, but you can afford a better class of enemy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385308: [Pkg-xen-devel] Bug#385308: Please provide way to run xend in the foreground, without daemonizing
On Wed, Aug 30, 2006 at 02:21:07PM +0200, Andras Korn wrote: it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). They are started by xend, so please provide concret informations. Bastian -- There's another way to survive. Mutual trust -- and help. -- Kirk, Day of the Dove, stardate unknown
Bug#385308: [Pkg-xen-devel] Bug#385308: Please provide way to run xend in the foreground, without daemonizing
On Wed, Aug 30, 2006 at 03:08:21PM +0200, Bastian Blank wrote: On Wed, Aug 30, 2006 at 02:21:07PM +0200, Andras Korn wrote: it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). They are started by xend, so please provide concret informations. I'm not sure in what way I wasn't specific enough, but anyway: What I do now is run xenconsoled and xenstored from runit, but xend still has to be started the System V init way. I'd like to run that under runit too. root 3953 Ss 11:26 0:00 runsvdir -P /var/service log: ... [...] root 3549 Ss 14:55 0:00 \_ runsv xenconsoled log 3626 S14:55 0:00 | \_ svlogd -t /var/log/sv/xenconsoled root 3847 Sl 14:57 0:00 | \_ /usr/sbin/xenconsoled -i root 3840 Ss 14:57 0:00 \_ runsv xenstored log 3841 S14:57 0:00 | \_ svlogd -t /var/log/sv/xenstored root 3843 S14:57 0:00 | \_ /usr/sbin/xenstored --no-fork root 5271 S15:26 0:00 python /usr/sbin/xend start root 5272 Sl 15:26 0:00 \_ python /usr/sbin/xend start This way xend doesn't start them, because they are already running by the time xend starts. (xend stop doesn't stop them in either case, which might be a bug, btw.) I can now do this: # sv status xenconsoled run: xenconsoled: (pid 3847) 3253s; run: log: (pid 3626) 3350s And runit restarts xenconsoled for me should it ever crash. Same for xenstored. I don't know enough about the architecture of xen to say whether it would be better to have xenconsoled and xenstored started by xend or not, I just know I'd like to get away from System V init and use runit to the extent possible. AFAICT now, having a foreground argument to xend (instead of start) is all that's needed. Andras -- Andras Korn korn at chardonnay.math.bme.hu http://chardonnay.math.bme.hu/~korn/ QOTD: Southern DOS: Y'all reckon? (yep/Nope) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
