THAT WORKED! Thanks! I was the victim of a bug!

On 1/25/2019 12:40 PM, Ian Kaufman wrote:
I believe you just need to update /etc/apparmor.d/usr.bin.man to include all of the necessary MAN paths.

This was a bug in apparmor that supposedly has been fixed, but depending on your patch level, it may not.

Anyway, according to the bug filed here:

https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1784499 <https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_ubuntu_-2Bsource_apparmor_-2Bbug_1784499&d=DwMFaQ&c=mkpgQs82XaCKIwNV8b32dmVOmERqJe4bBOtF0CetP9Y&r=EKk3zFVROsf8w5OyB2T6u55jzploih3y7CaWIlGOLAY&m=mdsj7Zr2pKODNxxFHlO66bhcti-yIpExwh5HCQVwYX0&s=0_ZDwalAY-XHCSZ41Y_8qvMa_XUjmy-jXQMxwsoEBu4&e=>

this is the fix for man pages:

Workaround (for /usr/bin/man only):

Add to /etc/apparmor.d/local/usr.bin.man the lines

  # TCP/UDP network access for NFS
  network inet stream,
  network inet6 stream,
  network inet dgram,
  network inet6 dgram,

then run

# systemctl reload apparmor

_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to