Summary: | Xprt permanently resets itself after each client disconnect | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xprint | Reporter: | Roland Mainz <roland.mainz> | ||||||||||||
Component: | Server: Config: startup scripts | Assignee: | Roland Mainz <roland.mainz> | ||||||||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||||||||
Severity: | critical | ||||||||||||||
Priority: | high | CC: | alan.coopersmith | ||||||||||||
Version: | unspecified | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | All | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Roland Mainz
2004-06-19 00:30:00 UTC
Created attachment 379 [details] [review] Patch for 2004-06-18-oldcvs_trunk Note that the patch backports the "-noreset" option of Xfree86 to the old codebase. attachment 379 [details] [review] checked-in... /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/Xprint/etc/init.d/xprint,v <-- xprint new revision: 1.53; previous revision: 1.52 /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/dix/dispatch.c,v <-- dispatch.c new revision: 1.3; previous revision: 1.2 /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/os/utils.c,v <-- utils.c new revision: 1.6; previous revision: 1.5 Created attachment 380 [details] [review] Patch for 2004-06-18-trunk attachment 380 [details] [review] checked-in into Xorg trunk... /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.64; previous revision: 1.63 /cvs/xorg/xc/programs/Xserver/Xprint/etc/init.d/xprint,v <-- xprint new revision: 1.9; previous revision: 1.8 Mailing the commit message to xorg-commit@pdx.freedesktop.org... ... marking bug as FIXED. Alan: Is there a chanche to get the "-noreset" option implemented into the Solaris Xserver's (Xsun, Xprt, etc), too ? Then there would no need anymore to add a special case for /usr/openwin/bin/Xprt (which still suffers from the problems described in comment #0 due lack of a -noreset option...). ? We can't add -noreset to the Solaris servers right now (we're in feature freeze), but this shouldn't be a problem for the Solaris Xprt in Solaris 9 and later, since the Solaris Xprt was changed in Solaris 9 to effectively do the same thing for Xprt. Alan Coopersmith wrote:
> the Solaris Xprt was changed in Solaris 9 to effectively do the same thing for
> Xprt.
Does it simply not reset or is that something like a "delayed" reset (e.g.
"reset only if the last client has left the boat and nothing has happend for
20secs") ?
I'll reopen the bug and adjust the Xserver code to default to "-noreset" for Xprt. Created attachment 381 [details] [review] Refix for 2004-06-18-oldcvs_trunk attachment 381 [details] [review] checked-in... /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/Xprint/etc/init.d/xprint,v <-- xprint new revision: 1.54; previous revision: 1.53 /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/dix/dispatch.c,v <-- dispatch.c new revision: 1.4; previous revision: 1.3 /cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/os/utils.c,v <-- utils.c new revision: 1.7; previous revision: 1.6 Created attachment 382 [details] [review] Refix for 2004-06-18-trunk attachment. 382 checked-in... /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.65; previous revision: 1.64 /cvs/xorg/xc/programs/Xserver/Xprint/Init.c,v <-- Init.c new revision: 1.5; previous revision: 1.4 /cvs/xorg/xc/programs/Xserver/Xprint/etc/init.d/xprint,v <-- xprint new revision: 1.10; previous revision: 1.9 /cvs/xorg/xc/programs/Xserver/os/utils.c,v <-- utils.c new revision: 1.3; previous revision: 1.2 Mailing the commit message to xorg-commit@pdx.freedesktop.org... ... marking bug as FIXED again. Created attachment 385 [details] [review] Fix for oldcvs_trunk RPM build bustage Roland Mainz wrote: > reated an attachment (id=385) > Fix for oldcvs_trunk RPM build bustage Sorry... that was the wrong bugid... the patch was for bug 765 (that mess happens when too many browser windows are open... ;-/) ... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.