Just came through... Ced
---------- Forwarded message ---------- From: John Moyer <[email protected]> Date: 6 September 2013 16:26 Subject: Bug#721986: ksh: Command history file corrupted when starting multiple ksh To: Debian Bug Tracking System <[email protected]> Package: ksh Version: 93u+-1.2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? ksh is login shell. On desktop, start multiple xterm -ls -sb -vb -geom 80x43 HISTFILE and HISTSIZE are set and HISTFILE contains at least HISTSIZE commands. (in my case HISTSIZE==20000 and more than 12 xterms). Log out saving desktop layout. When logging back into desktop, xterms are restarted in background. Each ksh checks whether HISTFILE needs to be truncated to HISTSIZE commands. There is a race condition and no lock between when ksh instances check size of HISTFILE and when they truncate it. Maybe flock would fix this? Work around: exit all but one xterm before logging out. So far as I can remember, this bug has existed since at least 1988 but did not often bother me until desktops started xterms in the background. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (10, 'testing'), (5, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ksh depends on: ii libc6 2.13-38 ksh recommends no packages. ksh suggests no packages. -- no debconf information -- Cedric Blancher <[email protected]> Institute Pasteur _______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
