I know it's a long time, but I'm cleaning up old NTP bugs atm.
Working fine these days and following the last posters request - closing
the bug as fix released.
** Changed in: ntp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/492734
Title:
ntpd profile in Xubuntu 8.04 LTS is unconfined on boot
Status in ntp package in Ubuntu:
Fix Released
Bug description:
When executing "aa-satatus" the program lists my trusty NTP daemon
(/usr/sbin/ntpd) within the last category "processes are unconfined
but have a profile defined". The NTP service is the only one listed
there!
After executing "sudo /etc/init.d/ntp restart" the NTP service is
being restarted. It is listed within the "processes are in complain
mode" category then, which is fine.
My question is whether I can change the NTP services startup time to
make sure it's App-Armor profile is always applied right after the OS
boot. Would that solve the problem at all?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/492734/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
