When lxc is emerged it create these two useless files: /etc/default/lxc: # LXC_AUTO - whether or not to start containers at boot LXC_AUTO="true" # BOOTGROUPS - What groups should start on bootup? # Comma separated list of groups. # Leading comma, trailing comma or embedded double # comma indicates when the NULL group should be run. # Example (default): boot the onboot group first then the NULL group BOOTGROUPS="onboot," # SHUTDOWNDELAY - Wait time for a container to shut down. # Container shutdown can result in lengthy system # shutdown times. Even 5 seconds per container can be # too long. SHUTDOWNDELAY=5 # OPTIONS can be used for anything else. # If you want to boot everything then # options can be "-a" or "-a -A". OPTIONS= # STOPOPTS are stop options. The can be used for anything else to stop. # If you want to kill containers fast, use -k STOPOPTS="-a -A -s" USE_LXC_BRIDGE="false" # overridden in lxc-net [ ! -f /etc/default/lxc-net ] || . /etc/default/lxc-net /etc/default/useradd: # useradd defaults file GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel $ equery belongs lxc * Searching for lxc ... ... app-emulation/lxc-1.1.2-r2 (/etc/default/lxc) ... This is most likely bug in lxc upstream, but we can at least remove it in ebuild. Reproducible: Always
I'm sorry, useradd file is from another package, so the problem is just /etc/default/lxc.
Like you said, this looks like an upstream bug. Did you report it upstream? I'd rather have this fixed upstream than messing with the ebuild.
Fixed in 2.0.1 ebuild. howarang, it is still possible for the package maintainer to file a bug with upstream, but this change can quickly keep users' systems a little cleaner.
