Github messages for voidlinux
 help / color / mirror / Atom feed
From: shahab-vahedi <shahab-vahedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Metalog bleeds onto tty1
Date: Thu, 31 Aug 2023 17:47:06 +0200	[thread overview]
Message-ID: <20230831154706.x9inZPyfnSw08toGClUutIUjwarykNXuDGTMPguIyOc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45653@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]

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.

  parent reply	other threads:[~2023-08-31 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:01 [ISSUE] " shahab-vahedi
2023-08-18  9:02 ` shahab-vahedi
2023-08-18 10:05 ` sgn
2023-08-18 10:40 ` jovanlanik
2023-08-18 15:05 ` shahab-vahedi
2023-08-18 15:06 ` shahab-vahedi
2023-08-21  8:28 ` shahab-vahedi
2023-08-21  8:28 ` shahab-vahedi
2023-08-21  8:28 ` shahab-vahedi
2023-08-21 15:48 ` aryandb
2023-08-21 15:48 ` aryandb
2023-08-26 20:41 ` gc-user
2023-08-31 15:46 ` shahab-vahedi
2023-08-31 15:47 ` shahab-vahedi [this message]
2023-08-31 17:52 ` gc-user

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230831154706.x9inZPyfnSw08toGClUutIUjwarykNXuDGTMPguIyOc@z \
    --to=shahab-vahedi@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).