[Date Prev][Date Next]
Re: cn=monitor && CS&T calendar
>>>>> "Rich" == Rich Graves <email@example.com> writes:
Rich> On Tue, 5 Dec 2000, Justin Banks wrote:
Rich> I didn't run into that problem. It "just worked," after I spent
Rich> a couple hours figuring out v3 schemas. Outline
Rich> What version of Calendar are you using? I have 5.1 on Linux.
The company currently has 3.5, and an upgrade (at least initially) is
not in the cards, alas. Perhaps that's my trouble. The real hurdle is
the lack of 'cn=monitor' availability, without which the unidasd
DEXOTEK ERRCODE Ox18030 -> ctldap_Open: Interoperability error
DEXOTEK ERRCODE Ox18030 -> das_Open: das_OpenDirConnection
DEXOTEK ERRCODE Ox18030 -> das_trh_Open: das_Open
DEXOTEK ERRCODE Ox11201 -> unidasd daemon: received SIGTERM
>> am I on my own here? Or, maybe I should take the easy route and
>> move back to 1.2.5 or so (thereby wasting all my attribute
>> definition effort), although I hate to move backwards.
Rich> Newer versions of CS&T (now Steltor) require LDAPv3, so you
Rich> can't move backwards.
Good. At least I have a reason to keep going forward ;)
My current tack is to define things as
attributetype ( foo-oid NAME 'foo'
DESC 'foo (for CS&T calendar)'
and I can then make the needed mods to monitor.c to get me past
this. Does anyone out there see a problem with this?
Justin Banks - WAM!NET Inc., Eagan MN firstname.lastname@example.org
#define private public // Information hiding in C++? Ha!