Bug 680 - RFE: /etc/init.d/xprint should ensure that the CWD is writeable for spooler applications
Summary: RFE: /etc/init.d/xprint should ensure that the CWD is writeable for spooler a...
Status: RESOLVED FIXED
Alias: None
Product: xprint
Classification: Unclassified
Component: Server: Config: startup scripts (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: Roland Mainz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 632
  Show dependency tree / graph
 
Reported: 2004-05-26 11:14 UTC by Roland Mainz
Modified: 2004-05-25 19:04 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Patch for 2004-05-26-oldcvs_trunk (1.80 KB, patch)
2004-05-26 11:16 UTC, Roland Mainz 		no flags Details | Splinter Review
View All

Description Roland Mainz 2004-05-26 11:14:07 UTC 
RFE: /etc/init.d/xprint should ensure that the CWD is writeable for spooler
applications.
It seems that some versions of CUPS require that the CWD is writeable for the
current UID.
Comment 1 Roland Mainz 2004-05-26 11:16:08 UTC 
Created attachment 324 [details] [review]
Patch for 2004-05-26-oldcvs_trunk
Comment 2 Roland Mainz 2004-05-26 11:17:51 UTC 
Patch checked-in into oldcvs_trunk...

Checking in xc/programs/Xserver/Xprint/etc/init.d/xprint;
/cvs/xprint/xprint/src/xprint_main/xc/programs/Xserver/Xprint/etc/init.d/xprint,v 
<--  xprint
new revision: 1.49; previous revision: 1.48
done

... leaving bug open for Xorg trunk.
Comment 3 Roland Mainz 2004-05-27 05:04:19 UTC 
Patch checked-in into Xorg trunk...

Checking in xc/ChangeLog;
/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.48; previous revision: 1.47
done
Checking in xc/programs/Xserver/Xprint/etc/init.d/xprint;
/cvs/xorg/xc/programs/Xserver/Xprint/etc/init.d/xprint,v  <--  xprint
new revision: 1.5; previous revision: 1.4
done
Mailing the commit message to xorg-commit@pdx.freedesktop.org...

... marking bug as FIXED.

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.