Bug 77002
Summary: | DB_File resets file timestamps when it should not | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <gauthier> |
Component: | perl | Assignee: | Warren Togami <wtogami> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-28 07:07:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-10-30 20:12:18 UTC
can you confirm the file on disk remained the same? it is possibly berkeley db doing some housekeeping on the file itself. the md5sum program can determine if a change takes place between invocations (moving to perl component; it isn't actually a DBI bug itself) Closing due to lack of activity and likely fixed in modern perl. If this is still an issue in RHEL4, FC3 or FC4 please open a new bug with new test information and exact versions of packages. |