Bug 74606 - CUPS severe failure mode if /var/tmp not writeable
Summary: CUPS severe failure mode if /var/tmp not writeable
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: cups (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-09-27 16:05 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-09-27 16:05:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2002-09-27 16:05:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
If /var/tmp is not writeable by the user attempting to print, and the user
invokes lpr reading from STDIN, the lpr process will spin out of control at 100%
CPU utilization and eventually consume all available memory, causing a kernel crash.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. chmod 755 /var/tmp (this was default on my install of RH 7.3)
2. alternatives --config print (select CUPS)
3. service lpd stop, service cups start
4. configure a cups printer via http://localhost:631
5. lpr (as non-priveleged user)

Actual Results:  CPU pegged, memory leaks, eventual crash of system

Expected Results:  lpr process should quietly wait for input

Additional info:

strace shows endless loop of 'error opening /var/tmp for write'

'chmod 1777 /var/tmp' fixes the problem, but this was not default permissions
for my install of RH 7.3.

this may indeed be a problem for CUPS developers to fix -- ie. graceful failure

Comment 1 Tim Waugh 2002-09-27 16:11:48 UTC
/var/tmp _must_ be writeable, and this is the default on all versions of Red 
Hat Linux. 
(See what 'rpm -V filesystem' says; for me it gives no output on a clean 

Note You need to log in before you can comment on or make changes to this bug.