I also hit this under Solaris 2.6 same lprng and gdbm versions.
I hit an infinite loop trying to run checkpc -f.

Running checkpc -f -V -D 3 gave:
[...]
2001-02-27-18:38:15.766 adminea01 [14554] checkpc  lp: Checkwrite: file 'db.lp', rw 2, 
create 1, nodelay 0
2001-02-27-18:38:15.794 adminea01 [14554] checkpc  lp: Checkwrite: file 'db.lp' fd 6, 
inode 0x17c, perms 0100600
2001-02-27-18:38:15.795 adminea01 [14554] checkpc  lp: Open_gdbm: gdbm_lock fd 6
2001-02-27-18:38:15.795 adminea01 [14554] checkpc  lp: Open_gdbm: locking 6
2001-02-27-18:38:15.795 adminea01 [14554] checkpc  lp: Do_lock: fd 6, block '1'
2001-02-27-18:38:15.796 adminea01 [14554] checkpc  lp: Do_lock: using lockf
2001-02-27-18:38:15.796 adminea01 [14554] checkpc  lp: Do_lock: status 0
[rinse, repeat...]

Sigh - I guess if things were meant to be simple, they wouldn't pay me what they do...

jk

From:  [EMAIL PROTECTED]
                      Date:  Thu Dec 28, 2000 1:05pm
                      Subject:  Re: LPRng: checkpc hangs on flock() call in 
lprng-3.7.3/Linux

                      ARGH...

                      It has not been a good week.

                      All I am going to say is 'put a test in a loop for success,  not 
just
                        failure'

                      > From [EMAIL PROTECTED] Wed Dec 27 12:21:03 2000
                      > From: Doug Morris <[EMAIL PROTECTED]>
                      > To: [EMAIL PROTECTED]
                      > Subject: LPRng: checkpc hangs on flock() call in 
lprng-3.7.3/Linux
                      > Date: Wed, 27 Dec 2000 19:59:45 +0100
                      >
                      > Hello LPRng-ers,
                      >
                      > I think I've found a bug in checkpc from lprng-3.7.3 (this 
didn't
                      > exist in 3.6.12, which I was running previously). I'd bet this 
is also
                      > the cause of the problem mentioned in a previous message 
"LPRng: lprng
                      > 3.7.3 rpm (checkpc) nad later lpd STARTALL problems", though 
I'm
                      > making some assumptions about what the rpm itself is doing on 
install,
                      > so don't hold me to it.
                      >
                      > I'm running Slackware Linux 7.1 with gdbm-1.8.0 and the 
as-delievred
                      > 2.2.16 #97 kernel. LPRng was built with the following options:
                      >


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to