From: goleo108 <goleo108@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] agetty, login: environment variables are pruned even when told not to do so
Date: Sat, 18 Jul 2020 10:11:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23640@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
New issue by goleo108 on void-packages repository
https://github.com/void-linux/void-packages/issues/23640
Description:
/etc/sv/agetty-generic/run as in arch linux's systemd doesn't work:
```
#!/bin/sh
tty=${PWD##*-}
[ -r conf ] && . ./conf
if [ -x /sbin/getty -o -x /bin/getty ]; then
# busybox
GETTY=getty
elif [ -x /sbin/agetty -o -x /bin/agetty ]; then
# util-linux
GETTY=agetty
fi
exec setsid ${GETTY} -o '-p -- \u' ${GETTY_ARGS} \
"${tty}" "${BAUD_RATE}" "${TERM_NAME}"
```
/etc/rc.local doesn't help either:
```
. /etc/profile
```
/etc/rc.conf is useless too:
```
. /etc/profile
```
slim doesn't prune those variables from /etc/rc.local or /etc/rc.conf because it's started at the correct phase of the moon
next reply other threads:[~2020-07-18 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 8:11 goleo108 [this message]
2021-01-21 18:15 ` ericonr
2021-01-21 18:15 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23640@inbox.vuxu.org \
--to=goleo108@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).