From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6076 invoked by alias); 19 Dec 2014 06:16:00 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19601 Received: (qmail 2861 invoked from network); 19 Dec 2014 06:15:47 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=b6gFOWC0 c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=zYOMLt5mkjHNNGxojQkA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141218221559.ZM28915@torch.brasslantern.com> Date: Thu, 18 Dec 2014 22:15:59 -0800 In-reply-to: <20141219052416.GA4570@solfire> Comments: In reply to meino.cramer@gmx.de "ZSH "killing" sdcard/flash memory..." (Dec 19, 6:24am) References: <20141219052416.GA4570@solfire> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: ZSH "killing" sdcard/flash memory... MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 19, 6:24am, meino.cramer@gmx.de wrote: } } Long story...short questions: } What is it, what makes the history mechanism of zsh constantly } "doing something" (closing/opening, writing, time stamping, } etc...anything what is filesystem related) with the filesystem, even } if there is no commandline to record? The shell should be blocked on read of standard input unless it is actively reading a command. Do you mean you're interacting with a shell that's running on this embedded system? Do you have something like strace you can connect to the shell with to see what system calls it is making? } How can I switch that off without lossing the history mechanism } itsselg? Make sure you don't have SHARE_HISTORY or INC_APPEND_HISTORY or INC_APPEND_HISTORY_TIME set -- but even those I'd only expect to be examining the history when the shell is actively doing something. Zsh does create and delete a lock file every time it needs to examine the history. In a recent shell you can try HIST_FCNTL_LOCK to see if that avoids the lock file creation.