| Summary: | app-misc/uptimed loses its database | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | jjtt <jjtt> |
| Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | orzel |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
patch from Debian Sid
patch from Debian Sid - bootid file is not needed on linux new ebuild applying the patches |
||
|
Description
jjtt
2012-04-12 18:37:03 UTC
Created attachment 308687 [details, diff]
patch from Debian Sid - bootid file is not needed on linux
The Debian package had another patch included which avoids creating a bootid file on linux and reads the information from /proc/stat
I tested both patches together, so I'll include them both in this bug report.
Created attachment 308689 [details, diff]
new ebuild applying the patches
And the trivial changes to the uptimed-0.3.16-r4.ebuild to apply the patches
I have had the same problem on several computers, all running ext4. it's reproducible : every unexpected shutdown/power off will remove the file and reset the history ticket at debian's: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474500 Does this still happen with uptimed-0.3.17? i'll report here when i know more, but i dont feel like doing a forced shutdown just for the sake of testing this bug :) (In reply to comment #5) > i'll report here when i know more, but i dont feel like doing a forced > shutdown just for the sake of testing this bug :) That was by no means what I wanted to request for. Just keep an eye on uptimed once the system experiences another uncommon shutdown. I'm setting this bug to TEST-REQUEST. If you find some similar situation like the ones this problem occured previously please report back if version 0.3.17 fixes this error. No response and no broken database on any of my machines yet so this seems to be fixed. |