Bug 214002 - Syncing hardware clock fails upon reboot
Summary: Syncing hardware clock fails upon reboot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: audit
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-04 13:43 UTC by Vladimir Kotal
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-06 15:37:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of the message (131.66 KB, image/jpeg)
2006-11-04 13:45 UTC, Vladimir Kotal
no flags Details

Description Vladimir Kotal 2006-11-04 13:43:53 UTC
Description of problem:
during evert shutdown/reboot an audit message is displayed about denied request
to synchronize hardware clock.

Version-Release number of selected component (if applicable):
libselinux-devel-1.30.29-2
selinux-policy-targeted-2.4.1-3.fc6
libselinux-1.30.29-2
libselinux-python-1.30.29-2
selinux-policy-2.4.1-3.fc6

How reproducible:
enable selinux and reboot

Actual results:
error message is displayed, request to synchronize hwclock is denied

Expected results:
the request should be allowed => no err message

Additional info:
Security policy is set to ´Permissive´

Comment 1 Vladimir Kotal 2006-11-04 13:45:03 UTC
Created attachment 140359 [details]
screenshot of the message

Comment 2 Vladimir Kotal 2006-11-04 13:46:28 UTC
Looking at the message once more now I see that res=success, however the message
is anoying anyway.

Comment 3 Daniel Walsh 2006-11-06 15:37:17 UTC
This is an audit message and believe it or not this has nothing to do with
SELinux.  Every time the hardware clock is changes the kernel generates an audit
message stating this.  If you do not have audit running at the time the message
is generated, it goes to syslog.

So if you want to complain, complain to the audit package. :^(


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