dtprobed: missing dtrace-usdt.target

[thesamesam]

# systemctl enable --now dtprobed
Failed to enable auxiliary unit dtrace-usdt.target, ignoring.

# equery f dtrace | grep -i usdt.target
#

[ezannoni]

What system is this on, we've never seen this...
Any clues to reproducing this?

[thesamesam]

This is on Gentoo with systemd. I could try give a Dockerfile to reproduce it, but see below...

In dtprobed/Build, we have:

install-dtprobed-autostart::
ifdef HAVE_LIBSYSTEMD
        mkdir -p $(INSTSYSTEMDUNITDIR) $(INSTSYSTEMDPRESETDIR)
        $(call describe-install-target,$(INSTSYSTEMDUNITDIR),dtprobed.service)
        sed 's,@SBINDIR@,$(SBINDIR),' < $(dtprobed_DIR)dtprobed.service.in > $(INSTSYSTEMDUNITDIR)/dtprobed.service
        chown root:root $(INSTSYSTEMDUNITDIR)/dtprobed.service
        chmod 0644 $(INSTSYSTEMDUNITDIR)/dtprobed.service
        $(call describe-install-target,$(INSTSYSTEMDUNITDIR),dtrace-usdt.target)
        install -m 644 $(dtprobed_DIR)dtrace-usdt.target $(INSTSYSTEMDUNITDIR)
        $(call describe-install-target,$(INSTSYSTEMDPRESETDIR),50-dtprobed.preset)
        install -m 644 $(dtprobed_DIR)50-dtprobed.preset $(INSTSYSTEMDPRESETDIR)
        if [[ -z $RPM_BUILD_ROOT ]]; then \
                systemctl enable dtprobed.service dtrace-usdt.target; \
        fi
endif

If we don't call install-dtprobed-autostart, which we don't in Gentoo, then we don't install the target at all. But what I don't get is, how is the service installed at all then? I don't see where that happens either, but I have it...

[nickalcock]

Err.. interesting question. I don't know the answer either :) that's the only place we install it! Residue from some previous run with different configure flags?