Creation of new ds instances with setup-ds.pl fail when user is not root.
Problem seems to be that setup-ds.pl tries to update systemd releted conf even when run as a user.
Simply skipping systemd stuff when user is not root fixes the problem:
in /usr/lib64/dirsrv/perl/DSCreate.pm update sub updateSystemD to include a uid check
[...] sub updateSystemD { my $inf = shift; my $unitdir = "/usr/lib/systemd/system"; my $confbasedir = "/etc/systemd/system"; my $confdir = "$confbasedir/dirsrv.target.wants"; if (!$unitdir or !$confdir or ! -d $unitdir or ! -d $confdir >>>>> or !(getLogin() eq 'root') <<<<< ) { debug(3, "no systemd - skipping\n"); return (); } [...]
Specific DS Version: 389-ds-base-1.3.0.2-1.fc18.x86_64
Per ticket triage: produce a wiki how-to with an INF file.
Possibly fixed with https://fedorahosted.org/389/ticket/48127
systemd can manage services under the user's control with a per-user systemd instance, enabling users to start, stop, enable, and disable their own units.
User can place services in {{{~/.config/systemd/user/}}} Units can be controlled by {{{systemctl --user}}}
For more details see: https://wiki.archlinux.org/index.php/Systemd/User
Per triage: this ticket is dup of #48127 except systemd.
https://fedorahosted.org/389/ticket/48127 is it already fixed
Note: for non-root installation, it's not allowed to use the standard install locaton, but all the available path info has to be provided.
Metadata Update from @nhosoi: - Issue assigned to tbordaz - Issue set to the milestone: 1.3.6 backlog
This will rely on linux capabilities so that we can correctly bind ports in ns-slapd without root. Additionally, we still need to run setup-ds either as dirsrv, or as root, so we probably need to check some permissions on paths to make sure we can do with with dirsrv.
Metadata Update from @mreynolds: - Custom field rhbz reset (from 0) - Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)
setup-ds.pl is deprecated, closing ticket
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/578
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.