[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: don't just seek to the next line if the script has been edited
From: |
jidanni |
Subject: |
Re: don't just seek to the next line if the script has been edited |
Date: |
Fri, 07 Jun 2013 22:15:46 +0800 |
>>>>> "GW" == Greg Wooledge <wooledg@eeg.ccf.org> writes:
GW> On Fri, Jun 07, 2013 at 09:09:53PM +0800, jidanni@jidanni.org wrote:
>> Well OK but sometimes a script could be running for years, during which
>> any change to a file will result in bash executing random bytes...
GW> This is why you don't edit an installed script in-place. Instead, you
GW> move it aside, or remove it, or hardlink it, or do some other fancy thing.
Well it is going to happen anyway, so maybe bash should check by
default, and not check if -o risky is set or something. It can't be that
expensive.
- don't just seek to the next line if the script has been edited, jidanni, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, Pierre Gaston, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, jidanni, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, jidanni, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, Chet Ramey, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, jidanni, 2013/06/07
- Re: don't just seek to the next line if the script has been edited, Linda Walsh, 2013/06/09
- Re: don't just seek to the next line if the script has been edited, Mike Frysinger, 2013/06/10
- Re: don't just seek to the next line if the script has been edited, Linda Walsh, 2013/06/10