Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1189205 > unrolled thread
| Started by | Anton Hvornum <torxed@archlinux.org> |
|---|---|
| First post | 2024-03-05 23:00 +0100 |
| Last post | 2024-03-05 23:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.bugs.dist
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1029675: faked daemon exits on SIGWINCH signal Anton Hvornum <torxed@archlinux.org> - 2024-03-05 23:00 +0100
| From | Anton Hvornum <torxed@archlinux.org> |
|---|---|
| Date | 2024-03-05 23:00 +0100 |
| Subject | Bug#1029675: faked daemon exits on SIGWINCH signal |
| Message-ID | <IeKZj-eFi3-3@gated-at.bofh.it> |
Most workarounds to the issue stipulates adding a docker workaround: --ulimit nofile=1024:524288 This only works in some instances, and this might be obvious to others.. But if running for instance makepkg[1] inside a docker container the issue will remain. Unless makepkg specifically was executed with ulimit. For instance (in the docker image): ulimit -n 1024 && makepkg -s Otherwise the ulimit on docker itself has little to no effect. [1] https://gitlab.archlinux.org/pacman/pacman/-/blob/e3dc296ba35d5039775c6e53decc7296b3bce396/scripts/makepkg.sh.in#L185-188
Back to top | Article view | linux.debian.bugs.dist
csiph-web