Thanks to all!

I didn't search very well into the bugs database. Sorry.

Jean-Paul, I took a look to your repos but I didn't find any emacs package.
I can only see:

   - 
emacs-doxymacs<http://ftp.lip6.fr/pub/linux/distributions/slsoc/soc/SRPMS/repoview/emacs-doxymacs.html>-
Doxygen
   add-on for Emacs/XEmacs
   - 
emacs-w3<http://ftp.lip6.fr/pub/linux/distributions/slsoc/soc/SRPMS/repoview/emacs-w3.html>-
W3
   package for Emacs


   - 
emacs-sdcc<http://ftp.lip6.fr/pub/linux/distributions/slsoc/soc/x86_64/repoview/emacs-sdcc.html>-
Emacs
   extensions for SDCC


But no emacs and emacs-common package.

Best regards.
Felip

2011/10/25 Stephan Wiesand <[email protected]>

> Hello Felip,
>
> On Oct 24, 2011, at 21:48, Felip Moll wrote:
>
> > Recently I installed a SL6.1 Cluster with 16 nodes, slurm resource
> manager, etc.
> >
> > I use Emacs to edit my files as do some of the researchers of my
> investigation center.
> >
> > One day I detected that some daemons hunged. I discovered that the kernel
> was killing some processes because the system went out of memory. I couldn't
> reproduce the error anymore, and the thing seemed to occurr on very random
> times.
> >
> > Since this day, I limited with limits.conf the user stack to 15Gb. (my
> server has 16gb, and consumes normally no more than 1gb).
> >
> > Today, when I was doing some tasks I could see what is causing the
> problem. It's Emacs!. There seems to be a user that uses emacs and that does
> logout from his session without exiting it. The access to the server is done
> by ssh.
> >
> > I will try to install the latest 23.3 version with .tar.gz package but I
> like to use the Yum package if it's possible in order to keep the
> installation as "clean as possible".
> >
> > Should I report it to some place?
>
> it seems someone else already has:
> https://bugzilla.redhat.com/show_bug.cgi?id=732157
>
> There's a proposed patch attached to that BZ.
>
> Regards,
>        Stephan
>
>
> --
> Stephan Wiesand
> DESY -DV-
> Platanenallee 6
> 15738 Zeuthen, Germany
>

Reply via email to