1546742558 Q * any0n Ping timeout: 480 seconds 1546745134 J * any0n ~k@0BGAAB602.tor-irc.dnsbl.oftc.net 1546746317 M * Bertl_oO off to bed now ... have a good one everyone! 1546746319 N * Bertl_oO Bertl_zZ 1546748303 Q * _pa Ping timeout: 480 seconds 1546758542 Q * any0n Ping timeout: 480 seconds 1546764419 M * Guy- daniel_hozac: yes, looking at an strace diff there is no obvious difference between vserver enter and vserver exec, except that setns() returns EINVAL when vserver exec calls it 1546764490 M * Guy- openat(AT_FDCWD, "/var/run/netns/foo", O_RDONLY|O_CLOEXEC) = 5 1546764490 M * Guy- -setns(5, CLONE_NEWNET) = -1 EINVAL (Invalid argument) 1546764490 M * Guy- +setns(5, CLONE_NEWNET) = 0 1546764978 M * Guy- daniel_hozac: also, why do you say the vserver netns stuff doesn't register the network namespace the same way as ip netns add? it seems to call ip netns add 1546764981 M * Guy- "$_IP" netns add "$name" 1546765040 M * Guy- (but strangely, /run/netns/foo isn't a mountpoint afterwards, whereas with plain ip netns add it would be) 1546765353 M * Guy- ah, and vserver foo exec calls ip netns exec, so it fails for the same reason ip netns exec fails 1546765816 M * Guy- I added a set -x to vserver.functions to obtain the effectivel command line vserver enter and vserver exec end up calling; but using those command lines I get the EINVAL in both cases, so there must be something magical vserver enter does before 1546765982 M * Guy- these are the two command lines, with spaces added to highlight the differences: http://sprunge.us/rK9D0S (but, as said, the magic that makes vserver enter work is not apparent here) 1546772948 J * romster ~romster@158.140.215.184 1546775023 Q * FloodServ Service unloaded 1546775089 J * FloodServ services@services.oftc.net 1546775282 Q * Aiken Remote host closed the connection 1546775405 M * Guy- daniel_hozac: I have it 1546775430 M * Guy- daniel_hozac: vserver exec does 'exec /usr/sbin/vspace --mount --fs --enter /etc/vservers/foo -- /usr/sbin/vserver ----nonamespace foo enter' before the 'ip netns exec' bit, and 'vserver exec' doesn't 1546775472 M * Guy- I'm guessing the /run/netns/foo mountpoint only exists in the mount namespace of the guest 1546775518 M * Guy- so this is probably really a problem with the mount namespace cleanup -- that mountpoint should be left alone 1546775996 M * Guy- adding "/run/netns" to /etc/vservers/foo/namespace-cleanup-skip avoids the problem; perhaps that path should be on the default skip list, at least when the netns mechanism is used? 1546776313 M * Guy- daniel_hozac: and 'vserver exec' should perhaps also use '/usr/sbin/vspace --mount --fs --enter /etc/vservers/foo' (but for 'ip netns exec' to work, the namespace cleanup still has to skip the /run/netns mountpoint) 1546781164 N * Bertl_zZ Bertl 1546781167 M * Bertl morning folks! 1546797454 J * any0n ~k@4JHAABI4W.tor-irc.dnsbl.oftc.net 1546799132 M * Bertl off for now ... bbl 1546799132 N * Bertl Bertl_oO 1546800812 J * Aiken ~Aiken@b951.h.jbmb.net 1546800876 J * fstd ~fstd@xdsl-87-78-187-119.nc.de 1546801326 Q * fstd_ Ping timeout: 480 seconds 1546803540 J * _pa ~pav@ec2-3-16-187-133.us-east-2.compute.amazonaws.com