On 11 May 2018 at 14:49, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > On Fri, 11 May 2018 08:36:09 -0400 > Tom H wrote: > >> Were some user services installed in $HOME? > > There wasn't anything in $HOME with the name '*grive*' > in it that find could find. Just the entries installed > by the package in /usr/lib/systemd/user > >> Do they show up with "systemctl --user"? > > They did indeed show up with the --user option, > but the --user option didn't seem to have any ability > to make them stop or disabled or any other kind > of manipulation. > > Anyway, with my "big hammer" of removing all the > files then rebooting, it seems to have stopped. > > Without rebooting it kept going even with the files > removed, so that's what I was wondering about. Is > there anything less drastic than rebooting to > convince systemd they are gone? IIRC, this worked for me before, though it was a long time ago and the details are a bit hazy in my mind: - Create ~/.local/share/systemd/user/ - Put a symlink, with the name of the offending systemd "user" service to /dev/null; technically this is like masking a regular systemd service. -- Ahmad Samir _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
