Bug 41652 - request: disable gdbm support and CFLAGS
Summary: request: disable gdbm support and CFLAGS
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: LPRng   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact: David Lawrence
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-21 18:19 UTC by Andreas J. Bathe
Modified: 2007-03-27 03:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-09 10:12:01 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 Andreas J. Bathe 2001-05-21 18:19:00 UTC
Description of Problem:
LPRng produces sometimes an interupted system call:
[...] Open_gdbm: cannot lock 'db.XXX' - Interrupted system call

How Reproducible:
Open_gdbm: cannot lock 'db.ps2' - Interrupted system call

The LPRng mailing list suggest to disable the gdbm support. And: Is the
debugging switch really necessary?

I suggest building the LPRng package with the following change:
< Release: 22
> Release: 23
< CFLAGS="-g" ; export CFLAGS
>       --disable-gdbm \

Take care

Comment 1 Need Real Name 2001-07-18 19:02:23 UTC
On my system this problem shows up once a month when we're trying to print
100-200 pages with invoices. Printing stops after a while. By adding a new
printjob printing resumes. In the log I see a whole buch of "cannot lock 'db.lp'
- Interrupted system call" messages.

BTW. Why do you think disabling gdbm solves the problem?

Comment 2 Andreas J. Bathe 2001-07-19 07:11:20 UTC
As I mentioned it above, I read this advice on the LPRng mailing list and since
I did it our company print- and faxserver which serves 6 printers behaves very
well since May 21th without any problems anymore.


Comment 3 Joerg Krause 2001-07-19 13:30:39 UTC
We have the same problem on some productions systems. If there are more than 100 Jobs in the queue LPRng stops
printing fopr that queue. After recompiling LPRng with the --disable-gdbm option everything works fine here.

Comment 4 Yong Chen 2001-08-08 19:46:23 UTC
Please give some instructions for rebuilding the packages.  Where to make those 
changes.  Thanks.

Comment 5 Andreas J. Bathe 2001-08-09 10:11:56 UTC
Change the spec file of LPRng with the diff information in the first comment and
rebuild the binary package with rpm -bb LPRng.spec (or whatever name you use).

Comment 6 Crutcher Dunnavant 2001-08-11 01:22:38 UTC
okay, next version.

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