Heh heh, doh. It's not my night... I just realized that those inodes
*aren't* the same. /me shuts up now
--
Free map of local environmental resources: http://CambridgeMA.GreenMap.org
--
MOTD on Sweetmorn, the 23rd of Discord, in the YOLD 3173:
When facism comes to America it will be wrapped in a f
>Minor note: hard links do not work across directories in AFS.
>This may be part of the problem you're seeing.
Really? (Not that it would surprise me)
% refile -link last +Trash +SPAM
% perl -le 'foreach( qw(/mit/belg4mit/Mail/SPAM/978
/mit/belg4mit/Mail/Trash/896) ){ print "$_: @{[stat $_]}: $!"
>* Assuming the system supports links, YMMV. AFS supports links, but -link
> has never worked for me; it's possible, but unlikely, that my folders
> live on different disks and linking would therefore be akin to linking
> across volumes.
Minor note: hard links do not work across directories in
Actually, my mind blanked and I sent the message before verifying a
test case. It seems it did just hardlink messages, but I seem to recall
this not always happening. Is the fallback to copy the message? If so,
a message to the user that this has happened would be nice.
--
Free map of local enviro
It seems to me that nmh commands ought to DWIM (do what I mean)
I know what the manual page says, but if I utter the following incantation:
refile +foo -link +bar
The message ought to be moved to foo and a link for it ought to be placed
in bar, as opposed to having links* from the current folde
> The reason dot locking is the default is because until fairly recently,
> fcntl locking wasn't a trustable option over NFS.
It still isn't, and dot locking needs to be in the nmh code for this
reason, IMHO.
When the locking code is revised (and it certainly needs to happen)
it should probably b
On Fri, 06 Apr 2007 13:45:35 EDT, Ken Hornstein said:
> >Tell your vendor to rebuild the package with fcntl locking. nmh uses dot
> >locking by default, which is pretty brain dead. Here is the option they
> >should give configure:
> >
> >--with-locking=fcntl
> >
> >So the question becomes, is the
>Tell your vendor to rebuild the package with fcntl locking. nmh uses dot
>locking by default, which is pretty brain dead. Here is the option they
>should give configure:
>
>--with-locking=fcntl
>
>So the question becomes, is there a reason we shouldn't fix configure to
>use fcntl locking by defa
> I recently installed nmh from a vendor package, on my home system. This
> is SuSE 10.1.
>
> % scan -version
> scan -- nmh-1.1-RC4 [compiled on e52 at Tue May 2 07:43:00 UTC 2006]
>
> Certain commands have long pauses before they do anything. In
> particular, I notice this for "se
I recently installed nmh from a vendor package, on my home system. This
is SuSE 10.1.
% scan -version
scan -- nmh-1.1-RC4 [compiled on e52 at Tue May 2 07:43:00 UTC 2006]
Certain commands have long pauses before they do anything. In
particular, I notice this for "send" and for
10 matches
Mail list logo
