9:32 p.m.
Hello
I am trying out slapo-dds. I haver this in slapd.conf:
overlay dds
dds-state TRUE
dds-max-ttl 1d
dds-min-ttl 10s
dds-default-ttl 1h
dds-interval 120s
dds-tolerance 5s
Then I created an entry with this:
objectClass: dynamicObject
I had this automatically generated.
entryTtl: 3600
entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What
is wrong? Did I misunderstood the documentation, shoudln't it vanish
now?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu(a)netbsd.org
6:50 a.m.
Emmanuel Dreyfus wrote:
Hello
I am trying out slapo-dds. I haver this in slapd.conf:
overlay dds
dds-state TRUE
dds-max-ttl 1d
dds-min-ttl 10s
dds-default-ttl 1h
dds-interval 120s
dds-tolerance 5s
Then I created an entry with this:
objectClass: dynamicObject
I had this automatically generated.
entryTtl: 3600
entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What
is wrong? Did I misunderstood the documentation, shoudln't it vanish
now?
Are there any more?
"the lifetime of dynamic objects with subordinates is prolonged until
all the dynamic subordinates expire."
--
Kind Regards,
Gavin Henry.
OpenLDAP Engineering Team.
E ghenry(a)OpenLDAP.org
Community developed LDAP software.
http://www.openldap.org/project/
11:21 a.m.
Gavin Henry <ghenry(a)OpenLDAP.org> wrote:
"the lifetime of dynamic objects with subordinates is prolonged
until
all the dynamic subordinates expire."
No subordinate:
entryTtl: 3600entry
ExpireTimestamp: 20081029215410Z
hasSubordinates: FALSE
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu(a)netbsd.org
8:20 p.m.
No hint for that problem? If I edit the expired object,
entryExpireTimestamp is set to the current time, but the object is still
there.
Emmanuel Dreyfus <manu(a)netbsd.org> wrote:
Hello
I am trying out slapo-dds. I haver this in slapd.conf:
overlay dds
dds-state TRUE
dds-max-ttl 1d
dds-min-ttl 10s
dds-default-ttl 1h
dds-interval 120s
dds-tolerance 5s
Then I created an entry with this:
objectClass: dynamicObject
I had this automatically generated.
entryTtl: 3600
entryExpireTimestamp: 20081029215410Z
But now this entry should be expired, and it is still in the tree. What
is wrong? Did I misunderstood the documentation, shoudln't it vanish
now?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu(a)netbsd.org
5:48 a.m.
Emmanuel Dreyfus wrote:
No hint for that problem? If I edit the expired object,
entryExpireTimestamp is set to the current time, but the object is still
there.
No clue. I think dds testing is pretty complete, takes care of all
cases. Did your build pass test046?
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
8:19 p.m.
Pierangelo Masarati <ando(a)sys-net.it> wrote:
No clue. I think dds testing is pretty complete, takes care of all
cases. Did your build pass test046?
This is on 2.4.11, not HEAD. It works fine on HEAD, I just tested it.
I finally found this;
DDS dn="cn=tmp,o=home" err=50; deferring.
DDS expired=0
Error 50 suggest I am blocked by an ACL??
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu(a)netbsd.org
10:53 p.m.
Emmanuel Dreyfus wrote:
Pierangelo Masarati <ando(a)sys-net.it> wrote:
> No clue. I think dds testing is pretty complete, takes care of all
> cases. Did your build pass test046?
This is on 2.4.11, not HEAD. It works fine on HEAD, I just tested it.
I finally found this;
DDS dn="cn=tmp,o=home" err=50; deferring.
DDS expired=0
Error 50 suggest I am blocked by an ACL??
Seems it. This message is printed after a delete failure. The only
recent change to ACL behavior was for add. I note that deletes are
performed by slapo-dds(5) as the rootdn, so unless you don't have a
rootdn configured they should always succeed.
This is not mentioned anywhere in slapo-dds(5), so probably it should be
documented.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
1:43 a.m.
Pierangelo Masarati <ando(a)sys-net.it> wrote:
Seems it. This message is printed after a delete failure. The only
recent change to ACL behavior was for add. I note that deletes are
performed by slapo-dds(5) as the rootdn, so unless you don't have a
rootdn configured they should always succeed.
This is not mentioned anywhere in slapo-dds(5), so probably it should be
documented.
Yes, that was the problem.
I opened ITS#5811 and committed a documentation fix.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu(a)netbsd.org
1:38 p.m.
----- "Emmanuel Dreyfus" <manu(a)netbsd.org> wrote:
No hint for that problem? If I edit the expired object,
entryExpireTimestamp is set to the current time, but the object is
still
there.
Nope, but Ando is the best person for this.
--
Kind Regards,
Gavin Henry.
OpenLDAP Engineering Team.
E ghenry(a)OpenLDAP.org
Community developed LDAP software.
http://www.openldap.org/project/
5495
days inactive
5511
days old
openldap-software@openldap.org
8 comments
3 participants
participants (3)
-
Gavin Henry -
manu＠netbsd.org -
Pierangelo Masarati