all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Hori <fplemma@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs leaves many .#file symlinks even after exiting from Emacs (related to file-locking)
Date: Sun, 17 Jan 2010 06:38:28 -0800	[thread overview]
Message-ID: <d0dc7c8f1001170638j29b8fbap902a52faeab192dd@mail.gmail.com> (raw)
In-Reply-To: <d0dc7c8f0912020107t506a9cccsbbb43206433a7f25@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

I received an email from someone who is also bothered by this
behavior (or should I call it a bug?).

Does anyone know how to prevent it?


On Wed, Dec 2, 2009 at 1:07 AM, Ken H. <fplemma@gmail.com> wrote:

>
> I cannot identify exactly under what conditions it occurs, but
> Emacs (I'm using CVS emacs on 2009-09-11, but would probably
> happen under CVS HEAD as well) leaves a lot of symlinks of the
> form:
>
>  .#file -> user_name@host_name.pid:boot_time
>
> `filelock.c' is creating the symlink for file-locking purposes
> but is failing to delete it.
>
> Under my current directory consisting of 28 regular files,
> I see three such instances:
>
>   lrwxrwxrwx   1 ken   ken     25 Oct 22 17:07 .#foo -> ken@hori.22964
> :1256147335
>   lrwxrwxrwx   1 ken   ken     25 Dec  1 22:32 .#foo2 -> ken@hori.19787
> :1259696496
>   lrwxrwxrwx   1 ken   ken     25 Dec  1 22:39 .#foo3 -> ken@hori.19787
> :1259696496
>
>
> Is this a bug that happens to people other than myself?  Or is it
> just me, who extensively use indirect buffers and work under
> multiple frames?  Also, if any, how do I prevent Emacs from
> creating such symlinks.
>
> Thanks.
>
>

[-- Attachment #2: Type: text/html, Size: 1483 bytes --]

  reply	other threads:[~2010-01-17 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02  9:07 Emacs leaves many .#file symlinks even after exiting from Emacs (related to file-locking) Ken H.
2010-01-17 14:38 ` Ken Hori [this message]
2010-01-17 16:37   ` Stefan Monnier

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=d0dc7c8f1001170638j29b8fbap902a52faeab192dd@mail.gmail.com \
    --to=fplemma@gmail.com \
    --cc=emacs-devel@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 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.