[389-users] Re: Using dsctl and .dscrc: How to properly connect to a remote instance?

> On 19 Apr 2023, at 15:53, Johannes Kastl <kastl@b1-systems.de> wrote:
>
> Hi William,
>
> thanks for the help.
>
> On 19.04.23 at 01:52 William Brown wrote:
>
>> dsctl requires root/dirsrv because it assumes you are on the same host as the dirsrv instance. There are three commands:
>
> Sorry, but then the documenation is... having need for improvement.

Which docs are you referring to here? For example:

https://www.port389.org/docs/389ds/howto/quickstart.html#our-commands

Pretty clearly states it :)

> I have misunderstood the purpose of the tools or the distinction between them.

That's okay - it's why they are seperate tools at all.

>
> Off the top if my head I am not sure what good "dsctl dsrc ..." is, if this does not work without a local instance?
>
>> dsctl - requires root/dirsrv, and tries to manipulate an instance directly via local system actions, things like dse.ldif and ldapi. It bypasses the uri provided, it's trying to "manage the system".
>> dsconf - required cn=Directory Manager and connects via the ldap uri.
>
> Ahh, and dsconf reads the .dsrc? Then I just picked the wrong tool, it seems.
>
> I was hoping to have a tool that gives me the status of a remote server or allows me to do healthchecks. Especially in Kubernetes, where entering the container is not something to be done on a daily basis. :-)
>
> I'll take a look at dsconf and see what it can do.
>

dsconf would be a better choice here as it can do some of these tasks. But some of the healthchecks do need local filesystem access which is why they are in dsctl.

>> dsidm - requires a bind dn with no aci's or limited write aci's in a backend and connects via ldap uri.
>
> dsidm does not read .dscrc, at least the manpage does not mention it. Does it have a config file? Or do I need to supply the connection information each time?

dsidm reads .dsrc the same as dsconf :)


>
> Kind Regards
> Johannes
>
> --
> Johannes Kastl
> Linux Consultant & Trainer
> Tel.: +49 (0) 151 2372 5802
> Mail: kastl@b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg
> http://www.b1-systems.de
> GF: Ralph Dehner
> Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

--
Sincerely,

William Brown

Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia

_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue