unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* emacs --daemon and M-x malloc-info
@ 2021-04-26  2:03 Madhu
  2021-04-26 11:48 ` Eli Zaretskii
  2021-04-26 12:00 ` Gregory Heytings
  0 siblings, 2 replies; 3+ messages in thread
From: Madhu @ 2021-04-26  2:03 UTC (permalink / raw)
  To: emacs-devel


Fmalloc_info writes to stderr, which is closed in a daemonized emacs.
How best to handle this? A new logfile argument to emacs or is there
some simple (if ugly) hack?




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: emacs --daemon and M-x malloc-info
  2021-04-26  2:03 emacs --daemon and M-x malloc-info Madhu
@ 2021-04-26 11:48 ` Eli Zaretskii
  2021-04-26 12:00 ` Gregory Heytings
  1 sibling, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2021-04-26 11:48 UTC (permalink / raw)
  To: Madhu; +Cc: emacs-devel

> From: Madhu <enometh@meer.net>
> Date: Mon, 26 Apr 2021 07:33:27 +0530
> 
> Fmalloc_info writes to stderr, which is closed in a daemonized emacs.

AFAIU, this happens only in the background daemon.  So using a
foreground daemon should allow you to redirect the output to a file.

> A new logfile argument to emacs

I don't see a reason to add a new knob, when there is already a
solution.  This is a diagnostic feature, so even if the daemon didn't
have a solution at all, I would hesitate adding a new option: you can
always run Emacs normally, and any serious memory related problem will
show itself in that configuration as well.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: emacs --daemon and M-x malloc-info
  2021-04-26  2:03 emacs --daemon and M-x malloc-info Madhu
  2021-04-26 11:48 ` Eli Zaretskii
@ 2021-04-26 12:00 ` Gregory Heytings
  1 sibling, 0 replies; 3+ messages in thread
From: Gregory Heytings @ 2021-04-26 12:00 UTC (permalink / raw)
  To: Madhu; +Cc: emacs-devel


>
> Fmalloc_info writes to stderr, which is closed in a daemonized emacs. 
> How best to handle this? A new logfile argument to emacs or is there 
> some simple (if ugly) hack?
>

On GNU/Linux systems, I would simply use "nohup emacs --fg-daemon &", 
which starts the daemon in foreground, detaches it from the terminal, and 
writes the output to a "nohup.out" file.  Or "nohup emacs --fg-daemon &> 
emacs-daemon.log &" to redirect output to the file "emacs-daemon.log" 
instead of "nohup.out".



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-04-26 12:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-26  2:03 emacs --daemon and M-x malloc-info Madhu
2021-04-26 11:48 ` Eli Zaretskii
2021-04-26 12:00 ` Gregory Heytings

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).