[Bug 558840] New: Start webyast client/service on demand (via xinetd)
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c0 Summary: Start webyast client/service on demand (via xinetd) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: WebYaST AssignedTo: kkaempf@novell.com ReportedBy: kkaempf@novell.com QAContact: qa@suse.de Found By: Development Blocker: --- I wonder why we're starting yastws/yastwc unconditionally via /etc/init.d as opposed to on demand via xinetd. The latter should have the advantage of a 'watchdog' around failing services. To be researched and documented -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c1 Stefan Schubert <schubi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |schubi@novell.com AssignedTo|kkaempf@novell.com |schubi@novell.com --- Comment #1 from Stefan Schubert <schubi@novell.com> 2009-12-03 10:37:57 UTC --- I will have a look -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c2 --- Comment #2 from Stefan Schubert <schubi@novell.com> 2009-12-07 09:03:08 UTC --- The code of xinetd is quite old. xinetd-2.3.14-129.28 is from 24 Oct. 2005. As far I have understood, processes have to be adapted to xinetd. For example Apache 1.3 supports xinetd Apache 2.0 does not. The problem is the port mapping. xinetd blocks the concerning port and start the service which is described in /etc/xinetd.d. This process has to be mapped to the already blocked port. I have tried to run lighty with xinetd and have gotten the error that the address is already in use. And it seems that lighty will not support xinetd in the future: http://redmine.lighttpd.net/issues/1584 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c3 Stefan Schubert <schubi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@novell.com --- Comment #3 from Stefan Schubert <schubi@novell.com> 2009-12-07 09:05:11 UTC --- Added Darix. Perhaps he has additional ideas :-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c4 Stefan Schubert <schubi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mseben@novell.com --- Comment #4 from Stefan Schubert <schubi@novell.com> 2009-12-07 09:08:02 UTC --- Added maintainer of xinetd. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=558840 http://bugzilla.novell.com/show_bug.cgi?id=558840#c5 --- Comment #5 from Marcus Rückert <mrueckert@novell.com> 2009-12-07 14:46:14 UTC --- starting a webserver over xinetd doesnt make much sense. especially when using fastcgi. it might make a little sense with ruby driven webservers like thin. but even then you launch the whole rails stack for e.g. delivering your CSS/js/image files. last but not least you have the long startup phase of the rails stack for almost every request. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com