I added a couple of extra debugging lines in mux.c, recompiled and ran
it.
debug3: link(
"/tmp/sshcontrol-f1b458a85cd2aa9d5c115abc12afee9f485ad6b0.XSLUj2BsBSDnTkhZ","/tmp/sshcontrol-f1b458a85cd2aa9d5c115abc12afee9f485ad6b0"
): 0
debug3: unlink(
"/tmp/sshcontrol-f1b458a85cd2aa9d5c115abc12afee9f485ad6b0.XSLUj2BsBSDnTkhZ" ): 0
The ": 0" is the value of the int returned by the two calls. They are
successful according to LINK(3POSIX) and UNLINK(3POSIX).
Seth Arnold is right. OpenSSH is doing the things in the right way.
But somehow the kernel (or could it be the libc?) is messing stuff
around with link() and/or unlink().
** Changed in: linux (Ubuntu)
Status: Opinion => Confirmed
** Changed in: openssh (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593657
Title:
ControlPath unix socket is created in a weird way
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
