From: Paul Pogonyshev <pogonyshev@gmail.com>
To: 21617@debbugs.gnu.org
Subject: bug#21617: Emacs compilation mode prevents child processes from spawning/forking daemons
Date: Mon, 5 Oct 2015 10:58:33 +0200 [thread overview]
Message-ID: <CAG7BpaqKornYbZ=SYvGopw9tj+VrByRjYLQUigror76kBsg5CQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
This can be reproduced with Gradle, but you don't need a Gradle project for
this. When running from a normal console:
$ gradle
Starting a new Gradle Daemon for this build (subsequent builds will be
faster).
:help
...
Total time: 2.014 secs
Now if I repeat it, the daemon is reused, so the first message is gone and
the "build" goes much faster:
$ gradle
:help
...
Total time: 0.495 secs
By comparison, when run from Emacs M-x compile, Gradle starts daemon every
time, so all builds look like the first example above. However, if daemon
already exists (e.g. created by console run above), it will not be killed.
File '~/.gradle/daemon/VERSION/daemon-PID.out.log' for daemons spawned
after M-x compile ends with this line:
Daemon vm is shutting down... The daemon has exited normally or was
terminated in response to a user interrupt.
When daemon is allowed to exist (e.g. when run from a normal console), log
receives this message instead:
... Daemon is idle, sleeping until state change or idle timeout at ...
Additionally, I checked several other ways to run process from Emacs:
* M-x eshell: daemon is killed, as with M-x compile
* M-x shell: daemon works properly
* M-!: daemon works properly
So, it seems that Emacs has a way to keep daemons alive / not kill them,
but it is not used in compilation mode.
Paul
[-- Attachment #2: Type: text/html, Size: 2023 bytes --]
next reply other threads:[~2015-10-05 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:58 Paul Pogonyshev [this message]
2015-10-05 9:25 ` bug#21617: Emacs compilation mode prevents child processes from spawning/forking daemons Eli Zaretskii
2015-10-05 9:43 ` Paul Pogonyshev
2016-06-14 21:51 ` Noam Postavsky
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='CAG7BpaqKornYbZ=SYvGopw9tj+VrByRjYLQUigror76kBsg5CQ@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=21617@debbugs.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.