Note that you're not supposed to write configuration like that to /lib/. I hope you (or another admin) simply created it there by mistake, and there is not a more complex problem. In that case you can just revert it, i.e.

rm /lib/systemd/system/getty.target.wants/[email protected]

Then you can reboot. (Or run systemctl daemon-reload, and check again to see that the service has been disabled properly).

Before deleting the file, I might double-check that the unwanted link is not provided by a package

dpkg-query -S /lib/systemd/system/getty.target.wants/[email protected]

and that it is indeed a symlink

ls -l /lib/systemd/system/getty.target.wants/[email protected]

You can also check for other files which were placed inappropriately by an admin. Install the Debian package cruft, and run cruft -d "/lib/systemd/system".

Following EDIT2, this answer is obsolete.

Note that you're not supposed to write configuration like that to /lib/. I hope you (or another admin) simply created it there by mistake, and there is not a more complex problem. In that case you can just revert it, i.e.

rm /lib/systemd/system/getty.target.wants/[email protected]

Then you can reboot. (Or run systemctl daemon-reload, and check again to see that the service has been disabled properly).

Before deleting the file, I might double-check that the unwanted link is not provided by a package

dpkg-query -S /lib/systemd/system/getty.target.wants/[email protected]

and that it is indeed a symlink

ls -l /lib/systemd/system/getty.target.wants/[email protected]

You can also check for other files which were placed inappropriately by an admin. Install the Debian package cruft, and run cruft -d "/lib/systemd/system".

Ok, you're not supposed to write configuration like that to /lib/. Hopefully you or another admin created it there by mistake, and there is not a more complex problem. In that case you can just revert it.

I might double-check that the unwanted symlink is not provided by a package

dpkg-query -S /lib/systemd/system/getty.target.wants/[email protected]

and that it is just a symlink

ls -l /lib/systemd/system/getty.target.wants/[email protected]

before deleting it

rm /lib/systemd/system/getty.target.wants/[email protected]

Then you can reboot, or you can run systemctl daemon-reload and check again to see the service has been properly disabled.

Note that you're not supposed to write configuration like that to /lib/. I hope you (or another admin) simply created it there by mistake, and there is not a more complex problem. In that case you can just revert it, i.e.

rm /lib/systemd/system/getty.target.wants/[email protected]

Then you can reboot. (Or run systemctl daemon-reload, and check again to see that the service has been disabled properly).

Before deleting the file, I might double-check that the unwanted link is not provided by a package

dpkg-query -S /lib/systemd/system/getty.target.wants/[email protected]

and that it is indeed a symlink

ls -l /lib/systemd/system/getty.target.wants/[email protected]

You can also check for other files which were placed inappropriately by an admin. Install the Debian package cruft, and run cruft -d "/lib/systemd/system".