Re: [trustees] Problem with settrustees -D

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Andrew Ruder a &eacute;crit&nbsp;:
<blockquote cite="mid...@bo..." type="cite">
  <pre wrap="">On Mon, Feb 05, 2007 at 01:21:54PM +0100, David Tassel wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hello,

I have had a problem with trustees for 2.6.18 kernel : The server crashed when I executed "settrustees -D".
This problem occured when the program settrustees has rebuilt its hash (message : "Rebuilding trustee hash, oldsize: 32, newsize 64"). 

I temporarily solved the problem changing "TRUSTEE_INITIAL_HASH_SIZE" from 32 to 1024 in .../include/trustees_private.h

If someone could find a better solution ...

Now, I will try to make trustees compatible with bind9 using "trustees &amp; capabilities together - ugly hack - From: Kamil Kaczkowski"

I hope that trustees will not be forgiven.

Regards

David
    </pre>
  </blockquote>
  <pre wrap=""><!---->
David,

I believe svn of trustees should have the capabilities stuff ready to
go.  I have been unable to reproduce the hash resizing issue, but I will
try again tonight.

Cheers,
Andy

  </pre>
</blockquote>
Hello,<br>
<br>
You're right, I solved the problem between trustees and bind9 by
changing the start order : I started trustees before bind9<br>
and although I had these messages when bind9 started :<br>
- Feb&nbsp; 9 08:35:14 sigsrvtest3 kernel: commoncap: exports duplicate
symbol cap_netlink_send (owned by trustees)<br>
- Feb&nbsp; 9 08:35:14 sigsrvtest3 kernel: Failure registering capabilities
with primary security module.<br>
I have made some tests and both services seem to work well.<br>
<br>
I'm glad to see that you can reproduce the hash problem. Good luck to
solve it !<br>
<br>
As far as I am concerned, I will try to stay with kernel 2.6.18 and
it's not a problem to compile the kernel with a patch.<br>
That what I have done with trustees v2 and all the 2.4.x kernel.<br>
<br>
David<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>