> Have you investigated this?
>
> May 28 15:47:20 adsl-64-216-197-92 identd[14702]: fopen("/proc/net/tcp",
"r"):
> Permission denied
>
>
> Isn't it msec which changes properties?
Is it msec, or is it the secure kernel? I could see it being either one.
>From a conversation between myself and Chmouel:
>> [root@big /etc]# tail -2 /var/log/messages
>> Jun 4 14:56:41 big in.identd[30631]: started
>> Jun 4 14:56:41 big in.identd[30631]: fopen("/proc/net/tcp", "r"):
>> Permission denied
>
> here is the point, secure kernel dont' allow you to use this procfile,
> you have to switch to the normal kernel
I will accept that as a temporary workaround. IMHO, this should not be
considered a permanent fix. I personally don't know that much about the
"secure" kernel. I've read the rpm -qi, and it talks about securing pieces
of /proc, "so that users may not see who else is logged on or what they are
doing". I'm not really too sure what this has to do with the file that
pidentd is trying to read, but it must have something (otherwise, why would
it be having this problem?). As I run a somewhat public system, the word
"secure" means a lot to me, so I'd prefer to use it.
It may be that Mandrake would want to look into one of the following:
- Modifying the secure kernel so that it doesn't interfere with pidentd.
- Finding another identd solution other than pidentd that doesn't require
access to that file.
- Something else I haven't thought of.
Don Head
Linux Mentor
Wave Technologies, Inc.
[EMAIL PROTECTED]
[AIM - Don Wave][ICQ - 18804935]
[IRC - EFnet, #WaveTech, Don-Wave]
