From: TrueTechie <TrueTechie@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Lightdm Ignores Limit Values
Date: Wed, 02 Nov 2022 21:33:23 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40305@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
New issue by TrueTechie on void-packages repository
https://github.com/void-linux/void-packages/issues/40305
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.17_1 x86_64 GenuineIntel uptodate FFFFF
### Package(s) Affected
pam-1.5.2_2 lightdm-1.32.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
After setting up Lightdm and modifying `/etc/security/limits.conf` and restarting the system, the output of `ulimit -Hn` should be the same as that defined in the configuration file.
For example, mine has the following line for playing games with ESync:
```
elliot hard nofile 524288
```
So the output of `ulimit -Hn` would be: `524288`
### Actual behaviour
No matter what is written in `/etc/security/limits.conf`, the output of `ulimit -Hn` is just the default of `4096`. According to [this issue](https://github.com/void-linux/void-packages/issues/20105) in 2020, this can be fixed by adding `session required pam_limits.so` to `/etc/pam.d/lightdm`. This should be enabled by default, but the issue was automatically closed due to inactivity.
### Steps to reproduce
1. Install and configure Lightdm
2. Set limits in `/etc/security/limits.conf`
3. Restart system
4. Log in via Lightdm
5. Run `ulimit -Hn`
next reply other threads:[~2022-11-02 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:33 TrueTechie [this message]
2023-02-20 0:42 ` bsduck
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-40305@inbox.vuxu.org \
--to=truetechie@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).