all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Trent W. Buck" <trentbuck@gmail.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 1058@emacsbugs.donarmstrong.com, rfrancoise@debian.org
Subject: bug#1058: 23.0.60; emacs --daemon should not return until socket is ready
Date: Thu, 2 Oct 2008 10:43:24 +1000	[thread overview]
Message-ID: <20081002004323.GA2400@Clio.twb.ath.cx> (raw)
In-Reply-To: <200810011651.m91GpAZQ010333@mothra.ics.uci.edu>

On Wed, Oct 01, 2008 at 09:51:10AM -0700, Dan Nicolaescu wrote:
>> From this transcript, you can see that after starting 'emacs
>> --daemon', it takes five seconds before the socket is actually
>> available for emacsclient to talk to it.
>>
>>   $ emacs --daemon; while ! ls /tmp/emacs1187/; do sleep 1; done
>
> Just curious, what do you get if you do:
>
> emacs -Q --daemon; while ! ls /tmp/emacs1187/; do sleep 1; done

I get the same problem.  Running c++ elsewhere and starting Emacs
nicely, I managed to get the delay up to 17 seconds.

$ nice -n 19 emacs -Q --daemon; until ls /tmp/emacs1187/; do sleep 1; done
ls: cannot access /tmp/emacs1187/: No such file or directory
[repeats 16 times]
server






      parent reply	other threads:[~2008-10-02  0:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 13:43 bug#1058: 23.0.60; emacs --daemon should not return until socket is ready SRS0+wOMF+22+gmail.com=trentbuck
2008-10-01 16:51 ` Dan Nicolaescu
2008-10-01 19:39   ` Romain Francoise
2008-10-01 20:19     ` Andreas Schwab
2008-10-02  6:05       ` Romain Francoise
2008-10-01 23:32     ` Dan Nicolaescu
2008-10-02  6:07       ` Romain Francoise
2008-10-02  8:14         ` Dan Nicolaescu
2008-10-02 12:38           ` Stefan Monnier
2008-10-02 17:26             ` Dan Nicolaescu
2008-10-02 21:32               ` Stefan Monnier
2008-10-02 22:34                 ` Dan Nicolaescu
2008-10-02 22:46                   ` Trent W. Buck
2008-10-03  1:12                   ` Stefan Monnier
2008-10-03  4:52                     ` Dan Nicolaescu
2008-10-03 13:00                       ` Stefan Monnier
2008-10-03 17:44                         ` Dan Nicolaescu
2008-10-13  2:03                     ` Dan Nicolaescu
2008-10-13 15:16                       ` Stefan Monnier
2008-10-13 17:01                         ` Dan Nicolaescu
2008-10-13 19:07                           ` Stefan Monnier
2008-10-14  7:26                             ` Dan Nicolaescu
2008-10-27  7:04                               ` Dan Nicolaescu
2008-10-02 22:42                 ` Trent W. Buck
2008-10-02 17:54           ` Romain Francoise
2008-10-02 18:40             ` Dan Nicolaescu
2008-10-06 20:59             ` Dan Nicolaescu
2008-10-07 14:26               ` Stefan Monnier
2008-10-07 15:31                 ` Dan Nicolaescu
2008-10-07 23:13                   ` Trent W. Buck
2008-10-08  2:03                     ` Stefan Monnier
2008-10-08  2:25                   ` Stefan Monnier
2008-10-07 18:45               ` Romain Francoise
2008-10-07 19:01                 ` Dan Nicolaescu
2008-10-26 19:24             ` Dan Nicolaescu
2008-10-02  0:50     ` Trent W. Buck
2008-10-02  0:43   ` Trent W. Buck [this message]

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=20081002004323.GA2400@Clio.twb.ath.cx \
    --to=trentbuck@gmail.com \
    --cc=1058@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    --cc=rfrancoise@debian.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.