> Do you have nscd installed inside the container (looking at the strace
> it appears you might have not).
I installed "unscd" instead of "nscd", as "unscd" is said to be less buggy.
> Is nscd installed outside of the container where you don't see the problem?
The host running container also use
Do you have nscd installed inside the container (looking at the strace
it appears you might have not).
Does it help if you install nscd?
Is nscd installed outside of the container where you don't see the problem?
signature.asc
Description: OpenPGP digital signature
The container is started as
systemd-nspawn -M bullseye --network-macvlan=eno1 -b
The option --network-macvlan=eno1 is necessary so that the container
can talk with the NIS server running on a third computer (not a container
nor the host running the container).
Ryutaroh
From: Ryutaroh Matsumoto
Hi Michael,
Thank you for paying attention to this.
> Do you have users/groups defined in
> /usr/lib/sysusers.d/ or /etc/sysusers.d which are only resolvable via NIS?
The above directories are untouched. The container was made by
mmdebstrap --variant=debootstrap bullseye.
/etc/passwd nor /etc/gro
Control: tags -1 + moreinfo
Hi!
Am 07.02.20 um 02:55 schrieb Ryutaroh Matsumoto:
> * the above hang-up does not happen if "nis" is removed from
> /etc/nsswitch.conf
> * the above hang-up is NOT observed outside a container.
> * I have no idea if it is an upstream issue.
> * Both host and contain
One more question:
Do you have users/groups defined in
/usr/lib/sysusers.d/ or /etc/sysusers.d which are only resolvable via NIS?
signature.asc
Description: OpenPGP digital signature
Processing control commands:
> tags -1 + moreinfo
Bug #950822 [systemd] systemd-sysusers hangs if nis is enabled in a
systemd-nspawn container
Added tag(s) moreinfo.
--
950822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hey Michael,
Apologies for taking a while to get back to you. Yay conference
week... :-/
On Mon, Feb 03, 2020 at 11:02:13AM +0100, Michael Biebl wrote:
>Am 03.02.20 um 09:59 schrieb Steve McIntyre:
>
>> ACL operation on "/var/log/journal" failed: No such file or directory
>> ACL operation on "/va
Hi Michael,
I had a look at the systemd source code. My aim is to make sure the
procps sysctl and the systemd sysctl behave the same way. The first problem
is we have a different order of things (/etc vs /run) so I looked at the
manual page first.
It looks like a lot of systemd programs have a
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #851243 (http://bugs.debian.org/851243)
> "Michael" == Michael Biebl writes:
Michael> b/ you need a different way to switch
Michael> over. Reboot into an environment for which you have control
Michael> over, then uninstall systemd/systemd-sysv without
Michael> triggering the removal of most packages.
This is fair
Processing control commands:
> tags -1 + fixed-upstream
Bug #950732 [src:systemd] systemd: CVE-2020-1712
Added tag(s) fixed-upstream.
--
950732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + fixed-upstream
Hi,
For completeness the following additional point:
On Wed, Feb 05, 2020 at 02:20:14PM +0100, Salvatore Bonaccorso wrote:
> The following vulnerability was published for systemd, filling bug to
> track the issue in BTS. Raised severity to RC, although the quest
Hi Craig
Am 06.02.20 um 12:31 schrieb Craig Small:
> Package: systemd
> Version: 244-3
> Severity: minor
> File: /usr/share/man/man5/sysctl.d.5.gz
>
> The sysctl.d.5 man page says this:
>
> Configuration files are read from directories in /etc/, /run/,
> /usr/local/lib/, and /lib/, in ord
Package: systemd
Version: 244-3
Severity: minor
File: /usr/share/man/man5/sysctl.d.5.gz
The sysctl.d.5 man page says this:
Configuration files are read from directories in /etc/, /run/,
/usr/local/lib/, and /lib/, in order of precedence. Each configuration file in
these configuration dire
16 matches
Mail list logo
