by Chris Webe » Wed, 22 May 1996 04:00:00
I have read the locks.txt file in the Documentation directory of the
latest kernel. I followed the directions and updated my libc to 5.3.12
and also updated the a.out libc to 4.7.6. Recompiled the kernel and
I still get these messages. What is the problem?
I looked at the files that it is complaining about and they are ELF-32
bit executables (lpd, etc.) Does anyone have an idea on how to correct
this problem? Any help would be be appreciated. Thank you.
Chris Weber
1. 1.3.95: fcntl_setlk() called by process 81 with broken flock() emulation
Those messages come from a change in fs/lock.c that just added a kprintf
statement. For all I can tell that code was executing silently in former
versions. This is hapening when agetty tries to lock the tty.
Francisco.
2. Linux & IRC
3. fcntl_setlk() called by process w/ broken flock() emulation
4. Anyone looking for a new position? just curious
5. fcntl_setlk() called by process 73 with broken flock emulation
6. bash: date of cmd in history file
7. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation
8. Xconfig and Compaq CDS 924 / Presario 140
9. 1.3.95: fcntl_setlk() called by process 81 with broken flock() emulation
10. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation
11. fcntl_setlk() called...w/ broken flock() emulation
12. fcntl_setlk() called... broken flock() emulation
13. fcntl_setlk() called with broken flock() emulation?