Bug: Failed to read initial configuration, open() syscall might be interrupted.

2016-10-10 Thread Andriy Prystupa
This was reproduced on Ubuntu 14.04 in VirtualBox. But I guess that issue exists on other distros. It is very timing dependent issue. Using Gdb or strace easily hide it. Our kernel has custom LSM. so open() syscall timing might be little bit changed some time. It has same effect as on slow devices

Re: Bug: Failed to read initial configuration, open() syscall might be interrupted.

2016-10-10 Thread Chet Ramey
On 10/5/16 9:04 AM, Andriy Prystupa wrote: > Hi, > > > Error: > > */bash: /etc/bash.bashrc: Interrupted system call /* > > Reproduced on bash-4.4 via *gnome-terminal* or *terminator* terminal. This is interesting. On what version of Unix/Linux is open(2) on a regular file from the local fil