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 m
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/ap
On 1/25/2019 11:02 AM, Fred Youhanaie wrote:
On 25/01/2019 14:24, David Triimboli wrote:
On 1/24/2019 5:25 PM, Fred Youhanaie wrote:
stat("/opt/sge/bin/qhost", 0x7fff16f8c7a0) = -1 EACCES (Permission
denied)
That's a strange line, because qhost lives in /opt/sge/bin/lx-amd64.
But the foll
On 1/25/2019 10:52 AM, Reuti wrote:
That's a strange line, because qhost lives in /opt/sge/bin/lx-amd64. But the
following line also has a permission denied message, and it points to the
correct location of qhost. But of course,
trimboli@ubuntuclient2:/opt/sge$ ls -l /opt/sge/bin/lx-amd64/qhos
On 25/01/2019 14:24, David Triimboli wrote:
On 1/24/2019 5:25 PM, Fred Youhanaie wrote:
stat("/opt/sge/bin/qhost", 0x7fff16f8c7a0) = -1 EACCES (Permission denied)
That's a strange line, because qhost lives in /opt/sge/bin/lx-amd64. But the
following line also has a permission denied message
> Am 25.01.2019 um 15:24 schrieb David Triimboli :
>
> On 1/24/2019 5:25 PM, Fred Youhanaie wrote:
>>
>> I can see "Permission denied" errors such as this one in the trace:
>>
>> openat(AT_FDCWD, "/opt/sge/man", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY)
>> = -1 EACCES (Permission denied)
>>
On 1/24/2019 5:25 PM, Fred Youhanaie wrote:
I can see "Permission denied" errors such as this one in the trace:
openat(AT_FDCWD, "/opt/sge/man",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 EACCES (Permission
denied)
I think it's worth revisiting the directory permissions, for each path
On 24/01/2019 20:29, David Triimboli wrote:
On 1/24/2019 2:54 PM, Fred Youhanaie wrote:
It seems the culprit is the man command, rather than the man pages themselves, since you
can "cat" the files directly.
The man command tends to consult other files and directories, such as manpath.config a
On 1/24/2019 3:04 PM, Reuti wrote:
Am 24.01.2019 um 20:29 schrieb David Triimboli:
On 1/24/2019 2:05 PM, Reuti wrote:
Do the permissions for the directories include the x flag and not only r?
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man1
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man3
drwxr-xr-
On 1/24/2019 2:54 PM, Fred Youhanaie wrote:
It seems the culprit is the man command, rather than the man pages
themselves, since you can "cat" the files directly.
The man command tends to consult other files and directories, such as
manpath.config and cache directories. It would be worth using
> Am 24.01.2019 um 20:29 schrieb David Triimboli :
>
> On 1/24/2019 2:05 PM, Reuti wrote:
>> Do the permissions for the directories include the x flag and not only r?
>>
>> drwxr-xr-x 2 root root 4.0K Jan 13 2010 man1
>> drwxr-xr-x 2 root root 4.0K Jan 13 2010 man3
>> drwxr-xr-x 2 root root 4
It seems the culprit is the man command, rather than the man pages themselves, since you
can "cat" the files directly.
The man command tends to consult other files and directories, such as manpath.config and cache directories. It would be worth using strace, e.g. strace man qhost, to see where t
On 1/24/2019 2:05 PM, Reuti wrote:
Do the permissions for the directories include the x flag and not only r?
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man1
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man3
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man5
drwxr-xr-x 2 root root 4.0K Jan 13 2010 man8
> Am 24.01.2019 um 19:28 schrieb David Triimboli :
>
> On 1/24/2019 1:14 PM, Reuti wrote:
>>> Am 24.01.2019 um 19:10 schrieb David Triimboli :
>>>
>>> On 1/24/2019 12:44 PM, Reuti wrote:
Hi,
> Am 24.01.2019 um 18:28 schrieb David Triimboli :
>
> This is just a silly quest
On 1/24/2019 1:51 PM, Reuti wrote:
Am 24.01.2019 um 19:28 schrieb David Triimboli :
On 1/24/2019 1:14 PM, Reuti wrote:
Am 24.01.2019 um 19:10 schrieb David Triimboli :
On 1/24/2019 12:44 PM, Reuti wrote:
Hi,
Am 24.01.2019 um 18:28 schrieb David Triimboli :
This is just a silly question.
> Am 24.01.2019 um 19:28 schrieb David Triimboli :
>
> On 1/24/2019 1:14 PM, Reuti wrote:
>>> Am 24.01.2019 um 19:10 schrieb David Triimboli :
>>>
>>> On 1/24/2019 12:44 PM, Reuti wrote:
Hi,
> Am 24.01.2019 um 18:28 schrieb David Triimboli :
>
> This is just a silly ques
On 1/24/2019 1:14 PM, Reuti wrote:
Am 24.01.2019 um 19:10 schrieb David Triimboli :
On 1/24/2019 12:44 PM, Reuti wrote:
Hi,
Am 24.01.2019 um 18:28 schrieb David Triimboli :
This is just a silly question. Using Son of Grid Engine 8.1.9, I installed a master and execution
host on one machine.
> Am 24.01.2019 um 19:10 schrieb David Triimboli :
>
> On 1/24/2019 12:44 PM, Reuti wrote:
>> Hi,
>>
>>> Am 24.01.2019 um 18:28 schrieb David Triimboli :
>>>
>>> This is just a silly question. Using Son of Grid Engine 8.1.9, I installed
>>> a master and execution host on one machine. The man
On 1/24/2019 12:44 PM, Reuti wrote:
Hi,
Am 24.01.2019 um 18:28 schrieb David Triimboli :
This is just a silly question. Using Son of Grid Engine 8.1.9, I installed a master and execution
host on one machine. The man pages work fine. I installed just an execution host on another. The
man page
Hi,
> Am 24.01.2019 um 18:28 schrieb David Triimboli :
>
> This is just a silly question. Using Son of Grid Engine 8.1.9, I installed a
> master and execution host on one machine. The man pages work fine. I
> installed just an execution host on another. The man pages aren't recognized;
> "man
This is just a silly question. Using Son of Grid Engine 8.1.9, I
installed a master and execution host on one machine. The man pages work
fine. I installed just an execution host on another. The man pages
aren't recognized; "man qhost" says "No manual entry for qhost." My
$MANPATH includes $SGE
21 matches
Mail list logo
