From: Florian von Savigny <florian265@uboot.com>
Subject: modifying movemail
Date: 19 Jun 2004 12:27:30 +0200 [thread overview]
Message-ID: <m33c4r3krx.fsf@uboot.com> (raw)
Rmail mode uses a small C program, movemail (movemail.exe on Win32),
to move mail from a spool file in Unix mbox format to an rmail file.
The problem I've got with it is actually a feature: it uses some kind
of file locking mechanism to prevent the spool file being accessed by
the mail fetching program at the same time. As strace has told me,
this seems to use some kind of link, but I don't even know if symbolic
or hard. In any case, this seems to be the reason why the spool file
cannot be on a FAT32 partition: movemail will get into an endless
cycle, trying over and over again to create some link, which the
kernel refuses with never-ending patience.
The reason why this is a problem is that I use both Emacs versions on
a dual-boot system (GNU/Linux and Win32), making it desirable to have
the spool files accessible under both OSes, and this is only possible
on a FAT32 partition.
>From what I said above, it seems evident that movemail.exe cannot
possibly use the same kind of file locking system as movemail (it
might be Win32 never permits two processes to modify the same file at
the same time, making any further measures superfluous, but who
knows). Since both appear to be compiled from the same source, I have
had a look at them, hoping to "disable" the file locking mechanism in
some way.
This seems, however, no trivial task, as so much in the emacs sources
understandably has multiple dependencies, and I haven't been able to
sort out the crucial difference between compiling movemail.c for Win32
and for Linux.
Could anybody provide guidance for me here? Or is the very idea flawed
in some way? I am well aware disabling the file locking mechanism
means in fact creating an unsafe program (or crippling it, as some
would probably put it), but this would pose no danger to my system as
it is set up. But it would spare me numerous reboots.
--
Florian v. Savigny
If you are going to reply in private, please be patient, as I only
check for mail something like once a week. - Si vous allez répondre
personellement, patientez s.v.p., car je ne lis les courriels
qu'environ une fois par semaine.
next reply other threads:[~2004-06-19 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 10:27 Florian von Savigny [this message]
2004-06-19 17:39 ` modifying movemail Pascal Bourguignon
2004-06-19 21:54 ` Florian von Savigny
2004-06-19 22:10 ` Pascal Bourguignon
2004-06-19 22:45 ` Florian von Savigny
2004-06-20 5:32 ` Pascal Bourguignon
2004-06-19 22:28 ` Florian von Savigny
2004-06-20 5:42 ` Pascal Bourguignon
2004-06-20 10:13 ` Florian von Savigny
2004-06-20 10:46 ` poor man's movemail Florian von Savigny
2004-06-21 13:26 ` modifying movemail Thien-Thi Nguyen
2004-07-01 10:17 ` Kai Grossjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33c4r3krx.fsf@uboot.com \
--to=florian265@uboot.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.