[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#418044: marked as done (cupssys: cups constantly updates the printcap file, preventing laptop_mode to spin down the disk)

Your message dated Sat, 6 Sep 2008 19:45:03 +0200
with message-id <20080906174503.GA3980@piware.de>
and subject line Re: cupssys: cups constantly updates the printcap file, preventing laptop_mode to spin down the disk
has caused the Debian Bug report #418044,
regarding cupssys: cups constantly updates the printcap file, preventing laptop_mode to spin down the disk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
418044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupssys
Severity: important

Since the last update on my laptop, cupsys keeps the disk spinning.
I tracked this down and identified that it writes its printcap file
regulary (and likely with a fsync()/fdatasync(), else it won't keep
the disk spinning). In my configuration cups logs to syslog, I did
not test if the logging would cause the same.

A workaround is to disable printcap generation in cups. But this is
certainly not a good solution.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20.4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message --- 
Version: 1.3.2-1

Christian Thaeter [2007-04-06 15:43 +0200]:
> Since the last update on my laptop, cupsys keeps the disk spinning.
> I tracked this down and identified that it writes its printcap file
> regulary (and likely with a fsync()/fdatasync(), else it won't keep
> the disk spinning). In my configuration cups logs to syslog, I did
> not test if the logging would cause the same.
> 
> A workaround is to disable printcap generation in cups. But this is
> certainly not a good solution.

This was fixed in cups 1.3.2, and thus in Lenny/Sid, see
http://www.cups.org/str.php?L2512.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

--- End Message ---
Reply to: