Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#482525: failure to fcntl-lock history file, takes ages to create interactive session



On Fri, May 23, 2008 at 11:46:36AM +0200, martin f krafft wrote:
> When I log in to a machine where my ~ is NFS-mounted (lockd is in
> use), with hist_fcntl_lock set, it takes several minutes to get an
> interactive prompt. The reason is that the locking seems to fail,
> according to strace:
> 
>   open("/home/madduck/.var/zsh/history-diamond", O_RDWR|O_NOCTTY) = 3
>   fcntl64(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 EIO (Input/output error)
>   rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
>   rt_sigaction(SIGCHLD, NULL, {0x80a88a0, [], SA_INTERRUPT}, 8) = 0
>   rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
>   nanosleep({1, 0}, {1, 0})         = 0 
> 
> This repeats a number of times before it finally moves on. Complete
> strace is attached. Search for "EIO".

Out of curiosity, does the same thing happen if you use -o nolock on the
client?



Messages sorted by: Reverse Date, Date, Thread, Author