From: Sven Joachim <svenjoac@gmx.de>
To: bug-gnu-emacs@gnu.org
Subject: bug#1736: [Hendrik Tews] movemail loops if hard links are not supported
Date: Tue, 30 Dec 2008 09:19:36 +0100 [thread overview]
Message-ID: <87d4fa5b3b.fsf@turtle.gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
On filesystems that do not support hard links, movemail will enter an
endless loop. It would probably be more prudent to error if link(2)
fails with EPERM.
[-- Attachment #2: Type: message/rfc822, Size: 2556 bytes --]
From: Hendrik Tews <tews@cs.ru.nl>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#384993: emacs21-bin-common: movemail loops if hard links are not supported
Date: Mon, 28 Aug 2006 13:18:22 +0200
Message-ID: <E1GHf8I-0001KX-PR@tandem.cs.ru.nl>
Package: emacs21-bin-common
Version: 21.4a-3
Severity: normal
movemail does not check the error code after creating the hard
link in line 344:
tem = link (tempname, lockname);
As a result it loops if the link fails with -1 EPERM (Operation
not permitted). This happens for instance on smbfs mounted
directories, because smbfs 3.0.22-1 does not support hard links
any more (it used to).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages emacs21-bin-common depends on:
ii emacs21-common 21.4a-3 The GNU Emacs editor's shared, arc
ii libc6 2.3.6-15 GNU C Library: Shared libraries
emacs21-bin-common recommends no packages.
-- no debconf information
Bye,
Hendrik
next reply other threads:[~2008-12-30 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874p0jl66v.fsf@cyd.mit.edu>
2008-12-30 8:19 ` Sven Joachim [this message]
2009-01-01 9:40 ` bug#1736: marked as done ([Hendrik Tews] movemail loops if hard links are not supported) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d4fa5b3b.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=1736@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).