Hi bill, Here is an user request. It seems to me a good idea, as FHS requests that as long as using HDB UUCP lock file format.
From: Marco Herrn <[EMAIL PROTECTED]> Subject: Bug#341250: gkrellm: lock file should be stored in /var/lock Date: Tue, 29 Nov 2005 16:18:51 +0100 > Package: gkrellm > Version: 2.2.7-5 > Severity: minor > > > Currently the lock is stored in the home dir of the user. This imposes > the problem that on a crash of the computer the lock file remains > there. So when trying to start gkrellm after that, gkrellm refuses to > start, because it finds a lockfile (if only one instance is allowed). > > I think it would be better to put lockfiles in /var/lock, since this > directory is cleaned on booting. > > To avoid complications, maybe the name of the user can be added to the > name of the lock file, for example: > lock_myuser_192.168.10.10:0.0 > > Regards > Marco > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.12-1-k7 > Locale: LANG=POSIX, [EMAIL PROTECTED] (charmap=ISO-8859-15) > > Versions of packages gkrellm depends on: > ii gkrellm-common 2.2.7-5 multiple stacked system > monitors: > ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit > ii libc6 2.3.5-8 GNU C Library: Shared libraries > an > ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime > libr > ii libglib2.0-0 2.8.3-1 The GLib library of C routines > ii libgnutls12 1.2.9-2 the GNU TLS library - runtime > libr > ii libgtk2.0-0 2.6.10-1 The GTK+ graphical user > interface > ii libice6 6.8.2.dfsg.1-7 Inter-Client Exchange library > ii libpango1.0-0 1.8.2-3 Layout and rendering of > internatio > ii libsm6 6.8.2.dfsg.1-7 X Window System Session > Management > ii libx11-6 6.8.2.dfsg.1-7 X Window System protocol client > li > ii xlibs 6.8.2.dfsg.1-7 X Window System client libraries > m > > gkrellm recommends no packages. > > -- no debconf information > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
