Mailinglist Archive: opensuse-security (575 mails)
| < Previous | Next > |
Re: [suse-security] SuSE Security Announcement: lprng/html2ps (SuSE-SA:2002:040)
- From: Dave <dave@xxxxxxxxxxx>
- Date: Tue, 05 Nov 2002 14:27:31 +0000
- Message-id: <3DC7D553.7090406@xxxxxxxxxxx>
Andreas Hasenack wrote:
In later RPM versions, there should always be __db* files in /var/lib/rpm once rpm has been run. Recovering from a freeze does involve deleting them to remove any stale locks, but their presence is normal.
FYI I'm already well aware both of recovery and the bug reports previously mentioned, and was merely trying to bring an existing problem to the lists' attention, as an alternative to the suggested bad package/bad hardware for lprng/html2ps (which incidentally I've had no problem with).
Dave
Alfar Networks
Em Tue, Nov 05, 2002 at 04:20:20AM +0100, Roman Drahtmueller escreveu:
>>The latest versions of rpm appear to have what is currently believed to be
>>either a race condition or stale lock problem that causes it to lock up in a
>>select call:
>>
>>select(0, NULL, NULL, NULL, {1,0}) = 0 (Timeout)
>>select(0, NULL, NULL, NULL, {1,0}) = 0 (Timeout)
>>etc.
>
>These select calls on NULL sockets are used as an equivalent to sleep(3)
>or usleep(2), nothing more. The suspicion about a deadlock holds, though,
This is a known problem with some RPM versions, check if you have some __db*
files in /var/lib/rpm.
In later RPM versions, there should always be __db* files in /var/lib/rpm once rpm has been run. Recovering from a freeze does involve deleting them to remove any stale locks, but their presence is normal.
FYI I'm already well aware both of recovery and the bug reports previously mentioned, and was merely trying to bring an existing problem to the lists' attention, as an alternative to the suggested bad package/bad hardware for lprng/html2ps (which incidentally I've had no problem with).
Dave
Alfar Networks
| < Previous | Next > |