Subject line about says it.
Didnt exactly disappear but became zero-length.
Checked because there seemed to nothing in the history.
Closed that shell and restarted.
The last shell's commands were there, nothing else
Wouldn't bother asking were it not for shellshock...
Debian jessie (with systemd
wrote:
> On 2009-08-13 10:00 +0200, paragasu wrote:
>
>> it is kind of weird when i checked my .bash_history, it is empty.
>
> Did your computer crash recently? Some filesystems (e.g. ext4 before
> kernel 2.6.30) might cause empty files under some conditions.
>
>> #s
On 2009-08-13 10:00 +0200, paragasu wrote:
> it is kind of weird when i checked my .bash_history, it is empty.
Did your computer crash recently? Some filesystems (e.g. ext4 before
kernel 2.6.30) might cause empty files under some conditions.
> #set give me
> HISTFILESIZE=500
>
it is kind of weird when i checked my .bash_history, it is empty.
#set give me
HISTFILESIZE=500
HISTSIZE=500
right now it work normal. after my last login it is not zero size anymore.
what i want to ask is, if the file (.bash_history) automatically empty
after the filesize reach 500KB?
--
To
On Wed, 26 Nov 2008, Boyd Stephen Smith Jr. wrote:
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export H
Am 2008-11-26 15:28:47, schrieb Robert Holtzman:
> I've been going thru a number of bash related web sites looking for the
> way to eliminate duplicates in ~/.bash_history. So far I've turned up
>
> export HISTCONTROL=ignoredups
> export HISTCONTROL=erasedups
>
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
> I've been going thru a number of bash related web sites looking for the
> way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export HISTCONTROL=ignoredups:erasedups
My .bash_history doesn
On Wed, Nov 26, 2008 at 5:28 PM, Robert Holtzman <[EMAIL PROTECTED]> wrote:
> I've been going thru a number of bash related web sites looking for the way
> to eliminate duplicates in ~/.bash_history. So far I've turned up
>
> export HISTCONTROL=ignoredups
> export
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
export HISTCONTROL=ignoredups
export HISTCONTROL=erasedups
awk '!x[$0]++' .bash_history > .bash.tmp && mv -f .bash.tmp .
On Tuesday 28 October 2008, "Robert Schmidli"
<[EMAIL PROTECTED]> wrote about 'Chkrootkit
reports "Warning: `//root/.bash_history' file size is zero"':
>I got the above message last night from chkrootkit. I haven't touched
>my /root/.bash_hist
I got the above message last night from chkrootkit. I haven't touched
my /root/.bash_history. Are there any programs that modify this?
There's no other evidence of a break-in.
I've confirmed that this file has zero size:
# cd
debian:~# ls -l .bash_history
-rw--- 1 root root
after crashes with JFS and
> XFS, but (almost? not sure) never with Ext3.
>
>
I have seen this today too, with my normal user account under X (debian
lenny | kernel 2.6.22.1). I use a crypted ext3 file system.
I worked in Eterm, and suddenly my history of the Eterm session was cut
off
Quoting Eduard Bloch <[EMAIL PROTECTED]>:
I have seen this several times in the past, still having no idea how
this happens. For a while I suspected bash_completion but I think I
saw this also without bash_completion. Finally I am suspecting the
filesystem journaling doing weird thin
Eduard Bloch wrote:
Hi Anna.
Anna Machens, 08.07.2007 15:48:
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly
there was no
history anymor
> Hi Anna.
>
> Anna Machens, 08.07.2007 15:48:
> > (i'm using debian unstable )
> > i am totally confused. suddenly, my .bash_history file for root did not
> > exist
> > anymore.
>
> That’s really odd; I experienced the same thing yesterday. S
Hi Anna.
Anna Machens, 08.07.2007 15:48:
> (i'm using debian unstable )
> i am totally confused. suddenly, my .bash_history file for root did not
> exist
> anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly there was no
history anymore but since t
hey,
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore. now, i've been checking for rootkits, sniffers, listening ports and
all that, and did not find anything suspicious. is it possible, that the
file
could
Oops; sorry about the line-length.
Hello,I'm running sarge.I rebooted this morning and root's bash history disappeared. I have a mail from a chkrootkit run by cron just before the reboot, and this doesn't flag it up, but a manual chkrootkit run just after the reboot did - that's how I discovered it. I can't see anything suspicious i
he history list.
>
> OK thanks.
by default the keybindings are from emacs -- helpful if you use emacs. can be
changed to work like the keystrokes in vi. read the section 'READLINE' in
'man bash'.
>
> I assume that my .bash_history gets converted to binary a
C. Chad Wallace on 22/11/05 02:38, wrote:
Stephen Rueger wrote:
Adam Hardy <[EMAIL PROTECTED]> writes:
This used to work until recently when I found that the .bash_history
had been transformed into a data file, instead of the ASCII text that
I was used to.
How exactly did you fin
Stephen Rueger wrote:
Adam Hardy <[EMAIL PROTECTED]> writes:
This used to work until recently when I found that the .bash_history had
been transformed into a data file, instead of the ASCII text that I was
used to.
How exactly did you find that out? If it's merely becaus
Adam Hardy <[EMAIL PROTECTED]> writes:
>This used to work until recently when I found that the .bash_history had
>been transformed into a data file, instead of the ASCII text that I was
>used to.
How exactly did you find that out? If it's merely because grep says
somethi
cuting the command from
the history list.
OK thanks.
I assume that my .bash_history gets converted to binary at some point by
bash. I can see that bash is using .bash_history now, but it's not clear
why the file should become binary on my system.
Adam
--
To UNSUBSCRIBE,
On Mon, Nov 21, 2005 at 10:00:33PM +, Adam Hardy wrote:
>
> thanks for the tips about C-r Is there some sort of documentation on this?
> I'd
> like to see how much history it keeps. It's a seperate program from history,
> right?
>
HISTSIZE
The number of commands to rem
Clive Menzies on 21/11/05 10:23, wrote:
On (20/11/05 21:41), Ralph Katz wrote:
On 11/20/2005 05:20 PM, Adam Hardy wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file fo
On Sun, 2005-11-20 at 23:45 +, Oliver Lupton wrote:
> On Sun, 20 Nov 2005 22:17:59 +
> Adam Hardy <[EMAIL PROTECTED]> wrote:
>
> > I rely on .bash_history alot to remind me what command syntax to use - I
> > don't scroll back thro the history wit
On (20/11/05 21:41), Ralph Katz wrote:
> On 11/20/2005 05:20 PM, Adam Hardy wrote:
> > I rely on .bash_history alot to remind me what command syntax to use - I
> > don't scroll back thro the history with the up button, I just grep the
> > .bash_history file for
On 11/20/2005 05:20 PM, Adam Hardy wrote:
> I rely on .bash_history alot to remind me what command syntax to use - I
> don't scroll back thro the history with the up button, I just grep the
> .bash_history file for the command I want to run.
>
> This used to work until recent
On Sun, 20 Nov 2005 22:17:59 +
Adam Hardy <[EMAIL PROTECTED]> wrote:
> I rely on .bash_history alot to remind me what command syntax to use - I
> don't scroll back thro the history with the up button, I just grep the
> .bash_history file for the command I want to run.
&g
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the command I want to run.
This used to work until recently when I found that the .bash_history had
been transformed i
On Fri, 2003-11-07 at 13:45, Mike Egglestone wrote:
> Hi,
> My server was trojaned recently, not sure how.
> It looks like /bin/ps was modified or replaced with
> a trojan.
> The /root/.bash_history file is set to this:
>
> chsslx1:~# ls -la .bash_history
> -rw-r
Quoting "J. Bruce Fields" <[EMAIL PROTECTED]>:
> On Fri, Nov 07, 2003 at 10:45:32AM -0800, Mike Egglestone wrote:
> > Hi,
> > My server was trojaned recently, not sure how.
> > It looks like /bin/ps was modified or replaced with
> > a trojan.
>
> Out of curiosity--how can you tell?
I could tell
On Fri, Nov 07, 2003 at 10:45:32AM -0800, Mike Egglestone wrote:
> Hi,
> My server was trojaned recently, not sure how.
> It looks like /bin/ps was modified or replaced with
> a trojan.
Out of curiosity--how can you tell?
> The /root/.bash_history file is set to this:
>
&
Quoting Andreas Janssen <[EMAIL PROTECTED]>:
>> Maybe the file is immutable. Check with
>
> lsattr .bash_history
>
> You can use chattr to change it:
>
> chattr -i .bash_history
Yes, that was it. It had a bunch of those permissions set.
I chattr'd them a
Hello
Mike Egglestone (<[EMAIL PROTECTED]>) wrote:
> My server was trojaned recently, not sure how.
> It looks like /bin/ps was modified or replaced with
> a trojan.
> The /root/.bash_history file is set to this:
>
> chsslx1:~# ls -la .bash_history
> -rw-r--r--1
Mike Egglestone wrote:
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov 7 05:31 .bash_history
and I can&#
Hi,
My server was trojaned recently, not sure how.
It looks like /bin/ps was modified or replaced with
a trojan.
The /root/.bash_history file is set to this:
chsslx1:~# ls -la .bash_history
-rw-r--r--1 root root0 Nov 7 05:31 .bash_history
and I can't edit it or dele
Hi,
I use Debian unstable. After booting up the machine in the morning, I
found that root's .bash_history file is missing.
Suspecting a break-in, I searched for any other traces, examined all
/var/log/* files thoroughly, did chkrootkit, tried to locate any
suspicious-looking files, proc
Sent: Sunday, October 22, 2000 12:16 AM
Subject: Re: bash_history
> I think you can turn saving of the history on/off, see man bash:
>
> ...
>HISTSIZE
> The number of commands to remember in the command
> history (see HISTORY below
which command history is
saved (see HISTORY below). The default value is
ß/.bash_history. If unset, the command history is
not saved when an interactive shell exits.
HISTFILESIZE
The maximum number of lines contained in the
Yes this is a typo! Do you have any answere of my questions?
- Original Message -
From: Moritz Schulte <[EMAIL PROTECTED]>
To:
Sent: Friday, October 20, 2000 10:30 PM
Subject: Re: bash_history
"Matthias Mann" <[EMAIL PROTECTED]> writes:
> Is there a bug in
"Matthias Mann" <[EMAIL PROTECTED]> writes:
> Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
> system the bash don´t save anything to /root/bash_history.
Is this a typo? Bash's history should be in ~/.bash_history.
moritz
--
/* Morit
Hi people!
Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
system the bash don´t save anything to /root/bash_history. Is this a bug or
default? If default, how can i configure my bash to save the history?
Have a nice day!
Matthias
Joey Hess wrote:
> Let's cut it down some..
>
> > cc anatomy.c -o anatomy
> > cc kod.c -o kofd
> > cp kofd kod
> > rm kofd
>
> According to google, kod and kofd are related to the oracle database.
> It's possible this is a cooincidence, or he was using these names to try
> to appear innocous (wei
"Dzuy M. Nguyen" wrote:
> This linux box was plugged into the same LAN as our company NT Network.
> It wasn't setup to access the NT Network or be involved in it. It just
> get's
> it's TCP/IP signal from the LAN.
And what about the internet connection? Are all of your NT boxes
connected directly
ave scanned the ports of the computers physically
connected on this LAN? Should I be concerned with the security of the
whole office now?
- Original Message -
From: w trillich <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 02, 2000 6:58 PM
Subject: Re: bash_history from Cracked Computer
Dzuy M. Nguyen wrote:
> Can someone help me figure out this "/.bash_history" from my
> computer that someone cracked into and did some damage.
>
> I'll probably re-install the box, but I'd like to see what they did
> before I destroy it. I've attached
if you run updatedb via cron (or run it from the shell by hand
recently) it'll tell you if you have any of the evil files
on your computer:
locate pscan
locate wuftp
locate bnc2
locate .shit
locate anatomy
locate kod
locate '/b$'
if you find a
is Romania)
It's unusual that he did a 'cat .bash_history', but didn't delete it.
Maybe it's a forgery?
Comments, people?
> "Dzuy M. Nguyen" wrote:
>
> Can someone help me figure out this "/.bash_history" from my
> computer that someone
Can someone help me figure out this
"/.bash_history" from my
computer that someone cracked into and did some
damage.
I'll probably re-install the box, but I'd like to
see what they did
before I destroy it. I've attached the
"/.bash_history".
Dzuy
w
Many thanks to all for help with this.
Patrick
> On Wed, 14 Jul 1999, Patrick Kirk wrote:
>
> > Hi all,
> >
> > I love the ability to get at previous commands just by flicking the up
> >arrow. But if the last 15 commands were mutt, its a little less
> >conenient. Is there a way that if the last 15 commands were ls preceded
> >by 10 mutts
Something that might help:
bash has both emacs and vi key bindings, and I think it defaults to emacs,
SO if you know that you used 'ls -stuFF' many commands ago, you can
type
ls
and bash will search backwards in the history list for the last time you
used ls and instantly take you there.
I use th
On Wed, Jul 14, 1999 at 09:23:12AM -0400, Michael E. Touloumtzis wrote:
> On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> > ... Is there a way that if the last 15 commands were ls preceded
> > by 10 mutts amd preceded by three tops, then the uparrow would
> > first show ls, then mu
Many thanks. I edited /etc/skel/.bash_profile and it is much easier now.
Patrick
On Wed, Jul 14, 1999 at 09:23:12AM -0400, Michael E. Touloumtzis wrote:
> On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> > ... Is there a way that if the last 15 commands were ls preceded
> > by 10
On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> ... Is there a way that if the last 15 commands were ls preceded
> by 10 mutts amd preceded by three tops, then the uparrow would
> first show ls, then mutt and then top?
man bash
export HISTCONTROL=ignoredups
Hi all,
I love the ability to get at previous commands just by flicking the up arrow.
But if the last 15 commands were mutt, its a little less conenient. Is there a
way that if the last 15 commands were ls preceded by 10 mutts amd preceded by
three tops, then the uparrow would first show ls,
58 matches
Mail list logo
