Re: dbus processes not being killed in RHEL6 when emacs24.4 exited

[Srikar Ananthula <ananthulasrikar@gmail.com>]

Hmm, I even tried to recompile the whole source code with the mentioned
option --without-dbus already , but even I facing the same problem.

The actual environment is we need to use this on grid engine servers, Hence
there are lot of users who opens emacs on them -> There might be lot of new
processes created but not terminated properly, which might eat resources.

Might be yes its good idea to write

~/.bash_logout script to solve this.


On Fri, Dec 19, 2014 at 1:09 AM, Glenn Morris <rgm@gnu.org> wrote:
>
> Srikar Ananthula wrote:
>
> > ananthul 19170     1  0 14:13 pts/3    00:00:00 dbus-launch --autolaunch
> > 9dc31ed
> > ananthul 19171     1  0 14:13 ?        00:00:00 /bin/dbus-daemon --fork
> > --print-
> >
> > Actual scenario : The processes have to be terminated as soon as I close
> > emacs. I hope its right.
> >
> > Present scenario : The processes are not being terminated,rather I need
> to
> > kill them manually using kill -9 command.
>
> Why do you care about these processes?
> Perhaps because of ssh? See eg
>
>
> http://serverfault.com/questions/405518/how-to-configure-d-bus-and-ssh-x-forwarding-to-prevent-ssh-from-hanging-on-exit
>
> Note that this is a general dbus issue rather than an Emacs issue.
> For example, the same thing happens with firefox on RHEL6.
> If you want an Emacs-specific solution, you could compile it
> --without-dbus.
>
> Rusi wrote:
>
> > There is this new wonder on earth called systemd.
>
> Of course, this is completely irrelevant for many reasons, not least of
> which is that RHEL6 use Upstart, not systemd.
>


-- 
~ srikar.io