Abir,
You wrote:
> I checked the files that Ubuntu's apparmor package provides and there aren't
> any rc*d scripts, only an init.d one.
Yes, that's correct. As is typical of debian (and other distributions')
packages, the post install script for the apparmor package sets up the
rc*d symlinks at install time; for the apparmor package it should be
setting up an appropriate symlink in the /etc/rcS.d directory (it does
"update-rc.d apparmor start 37 S .").
Looking at the rc directory tarball you attached, the rcS.d/ directory
does not contain the apparmor symlink, which is why most of the apparmor
policy is not getting loaded at boot. You can fix this for your system
by running the command above as root (e.g. "sudo update-rc.d apparmor
start 37 S .").
The real question is how did your system get into the state where it was
not enabled. How did you install this system? Has it always been failing
to load the apparmor policy since it was installed?
Thanks.
** Changed in: apparmor (Ubuntu)
Status: New => Incomplete
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805731
Title:
aa doesn't load profiles on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/805731/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
