[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [linux_var] ssh malloc error

To: linux_var - LUG di Varese e Provincia Mailing List <talking@ml.linuxvar.it>
Subject: Re: [linux_var] ssh malloc error
From: "Mr. P|pex" <gianluca@pipex.name>
Date: Sun, 20 Nov 2016 11:33:56 +0100
Authentication-results: linuxvar.it; dkim=pass reason="2048-bit key; unprotected key" header.d=pipex-name.20150623.gappssmtp.com header.i=@pipex-name.20150623.gappssmtp.com header.b=hnlBSnte; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Delivered-to: diegor@tiscali.it
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ml.linuxvar.it; s=mail; t=1479638060; bh=q7+UERa4DRx7Bx5ftp5Ct9hf1onKxDs+yyKCFKhr5lI=; h=In-Reply-To:References:From:Date:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Reply-To; z=In-Reply-To:=20<20161018224146.b9c079def3ee5de1300b43b3@gmx.co.uk >|References:=20<CAFzX3+fMwYrsUECyAycfUtHVsshqj_A6qygMwiUj1CD5kFXj Zg@mail.gmail.com>=0D=0A=20<20161018221710.4282bec5440eabd4fc30f84 7@tiscali.it>=0D=0A=20<20161018224146.b9c079def3ee5de1300b43b3@gmx .co.uk>|From:=20"Mr.=20P|pex"=20<gianluca@pipex.name>|Date:=20Sun, =2020=20Nov=202016=2011:33:56=20+0100|To:=20linux_var=20-=20LUG=20 di=20Varese=20e=20Provincia=20Mailing=20List=20<talking@ml.linuxva r.it>|Subject:=20Re:=20[linux_var]=20ssh=20malloc=20error|List-Id: =20linux_var=20-=20LUG=20di=20Varese=20e=20Provincia=20Mailing=20L ist=0D=0A=20<talking.ml.linuxvar.it>|List-Unsubscribe:=20<http://m l.linuxvar.it/cgi-bin/mailman/options/talking>,=0D=0A=20<mailto:ta lking-request@ml.linuxvar.it?subject=3Dunsubscribe>|List-Archive:= 20<http://ml.linuxvar.it/pipermail/talking/>|List-Post:=20<mailto: talking@ml.linuxvar.it>|List-Help:=20<mailto:talking-request@ml.li nuxvar.it?subject=3Dhelp>|List-Subscribe:=20<http://ml.linuxvar.it /cgi-bin/mailman/listinfo/talking>,=0D=0A=20<mailto:talking-reques t@ml.linuxvar.it?subject=3Dsubscribe>|Reply-To:=20linux_var=20-=20 LUG=20di=20Varese=20e=20Provincia=20Mailing=20List=0D=0A=20<talkin g@ml.linuxvar.it>; b=QBQmdJIXsqTde2KX4iAOPZOIaHIJCVEB7Glb/fCH+SBSONkeXdHj62/cpBHNGHsYd zJFh344izFG5NTeJrRqhMz5p5tn8ceG/yrFo7s3LIJpD+DWJlo7AuYvSrJeHPD6nb4 IN7DVUrBAAAZRO0rVW74L9kQgCRD00EKZ+TwoeR4=
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pipex-name.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=0KyNSOEEyhx2liohfxiknKtcHIKpCZd83wdpNsBTJzM=; b=hnlBSnteuQhuDqa0WrGYAAeHTl9ydANBJQv9bm72+b3s+XPGl3BliyEJ7oDG3S5TRC BolJWPERSTjEkfNRJ2iUiMAAC/5EJJLe3B51QVkj4tmSsWaGjSJv0fBmCGAKkrphogs2 wsl51Dtz+8fw/8Q2nsGzVyml+/KOC7DsOodnrwUwBd6xNz4Fkv3PPBBlgqbZGKCBxdRI 6M/vFtYa11xTP2d6ORbVRq7ikuA70peYb8T1AqVsadxFX9VQF/nQcAxWUnkWgB0zulPc papIQ3aJNP0MrVxbD7WN85r6a/BZjDaNG+sDM7/qhbEoNiA2eHafYgU9OtPBTA3MSMj5 WSYg==
In-reply-to: <20161018224146.b9c079def3ee5de1300b43b3@gmx.co.uk>
List-archive: <http://ml.linuxvar.it/pipermail/talking/>
List-help: <mailto:talking-request@ml.linuxvar.it?subject=help>
List-id: linux_var - LUG di Varese e Provincia Mailing List <talking.ml.linuxvar.it>
List-post: <mailto:talking@ml.linuxvar.it>
List-subscribe: <http://ml.linuxvar.it/cgi-bin/mailman/listinfo/talking>, <mailto:talking-request@ml.linuxvar.it?subject=subscribe>
List-unsubscribe: <http://ml.linuxvar.it/cgi-bin/mailman/options/talking>, <mailto:talking-request@ml.linuxvar.it?subject=unsubscribe>
References: <CAFzX3+fMwYrsUECyAycfUtHVsshqj_A6qygMwiUj1CD5kFXjZg@mail.gmail.com> <20161018221710.4282bec5440eabd4fc30f847@tiscali.it> <20161018224146.b9c079def3ee5de1300b43b3@gmx.co.uk>
Reply-to: linux_var - LUG di Varese e Provincia Mailing List <talking@ml.linuxvar.it>
Sender: "Talking" <talking-bounces@ml.linuxvar.it>

Il 18 ottobre 2016 22:41, Riccardo Macoratti <r.macoratti@gmx.co.uk> ha scritto:
>> Apparentemente la bash che parte dopo che ti logghi cerca di allocare 11Gb. Interessante ...
>
> Quoto. Prova a controllare cosa c'è di strano nei ~/.bashrc, ~/.profile, /etc/profile.
>
> Oppure se cerchi di eseguire uno script, controlla lo script, potrebbe fare qualcosa che può allocare moooolta RAM. (http://stackoverflow.com/questions/32235683/xmalloc-error-in-bash)

ciao
avevo risolto quasi subito dopo aver letto e controllato

in /etc/profile.d/mioscript.sh

avevo impostato i parametri per la history (questo file è così
impostato da quando ho reinstallato il pc, nel 2009)

EDITOR=/usr/bin/emacs
TMOUT=600
HISTFILE=~/.bash_history
#       HISTSIZE=10000000000
#       HISTFILESIZE=10000000000
readonly HISTFILE
readonly HISTSIZE
readonly HISTFILESIZE
export HISTFILE HISTSIZE HISTFILESIZE TMOUT EDITOR

le 2 righe commentato davano il problema. Non ho indagato
ulteriormente e sto cercando di capire . Qualche indicazione? sono
ancora utili e valide queste impostazioni?

saluti
GM
_______________________________________________
Talking mailing list
Talking@ml.linuxvar.it
http://ml.linuxvar.it/cgi-bin/mailman/listinfo/talking

Follow-Ups:
- Re: [linux_var] ssh malloc error
  - From: Diego Roversi <diegor@tiscali.it>

References:
- [linux_var] ssh malloc error
  - From: "Mr. P|pex" <gianluca@pipex.name>
- Re: [linux_var] ssh malloc error
  - From: Diego Roversi <diegor@tiscali.it>
- Re: [linux_var] ssh malloc error
  - From: Riccardo Macoratti <r.macoratti@gmx.co.uk>

Prev by Date: Re: [linux_var] Debian. Grandi pulizie. Rimuovere pacchetti "RC"
Next by Date: [linux_var] Trigger javascript-php
Previous by thread: Re: [linux_var] ssh malloc error
Next by thread: Re: [linux_var] ssh malloc error
Index(es):
- Date
- Thread