Closed issue by shahab-vahedi on void-packages repository

https://github.com/void-linux/void-packages/issues/45653

Description:
### Is this a new report?

Yes

### System Info

Void 6.3.13_1 x86_64 GenuineIntel uptodate hold rrrmdDDFFFFFF

### Package(s) Affected

metalog-20230719_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No to the best of my knowledge.

### Expected behaviour

TTY1 console should remain intact from the system level logs.

Version `20220214` is fine. I noticed this behavior on `20230719`. I never tried version `20230707` though.

### Actual behaviour

Below is a sample output of my default virtual console (`agetty-tty1`). What I do is:

1. Login to the system which results in logs being shown on the output.
2. Perform a user level command (`ls`) which goes OK.
3. Repeating step 2 command with privilege (`doas`) which results in system level logging that ends up in the console.
4. Disabling the `metalog` service.
5. Repeating step 3 without any pollution. 

```
Login: edie
Password:

Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [kernel] [ 2540.865203] elogind-daemon[1779]: New session 4 of user edie.
Last login: Fri Aug 18 09:46:38 on tty1
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie

$ ls
a  b

$ doas ls
doas (edie@laptop) password:
Aug 18 09:58:27 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:27 [doas] edie ran command ls as root from /home/edie/test
a  b
Aug 18 09:58:27 [doas] pam_unix(doas:session): session closed for user root

$ doas sv stop metalog
Aug 18 09:58:55 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:55 [doas] edie ran command sv stop metalog as root from /home/edie/test
ok: down: metalog: 0s, normally up

$ doas ls
a  b
```


### Steps to reproduce

1. Have the service enabled.
2. Drop into your default virtual console (`agetty-tty1`).
3. You're going to immediately see all the system logs polluted into the console's output.