Re: command line history

2002-12-26 Thread Matthew Boeckman
this can also be set with the environment variable HISTFILE. whatever file you set HISTFILE to use must be writable by the user invoking the shell. try 'man bash' for more info Mike Burger wrote: Set the user shell to bash, which stores the command history in ~/.bash_history On 26 Dec 2002,

command line history

2002-12-25 Thread shawn
when I work as root I get a nice history of the commands I've done on the command line. that dissappears when I am just a user. I don't need the root history but just that for the user. how can I set it so that the command line with remember the commands I do as a user too? TIA, Shawn --

Re: command line history

2002-12-25 Thread Mike Burger
Set the user shell to bash, which stores the command history in ~/.bash_history On 26 Dec 2002, shawn wrote: when I work as root I get a nice history of the commands I've done on the command line. that dissappears when I am just a user. I don't need the root history but just that for the

Re: Autorun, alarm daemon and history (command line history)

2002-02-07 Thread Alan Peery
David Talkington wrote: KDE is a marvel. It is a deeply integrated, logically organized, visually striking, feature-laden, polished interface, in all the 3D-widget, fading-tooltip, anti-aliased-font glory people have come to expect from their business desktops. And it's become equally

RE: Autorun, alarm daemon and history (command line history)

2002-02-06 Thread Ismael Touama
Devon Envoyé : mercredi 6 février 2002 07:01 À : [EMAIL PROTECTED] Objet : Re: Autorun, alarm daemon and history (command line history) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 06 February 2002 12:37 am, David Talkington wrote: Devon wrote: Click the icon on the right hand side

Autorun, alarm daemon and history (command line history)

2002-02-05 Thread Ismael Touama
Hi it's me again, always boot or shutdown problems for new linux user! At boot, after load, my KDE tool bar indicates 3 processes (?) running: -Autorun -alarm daemon -history for command line ('historique du presse-papier' in french) How can I cancel these processes? It seems it consumes

Re: Autorun, alarm daemon and history (command line history)

2002-02-05 Thread aftab alam
Daemon is generally disabled from the directory /etc/rc5.d if you are running X otherwise from /etc/rc3.d. You have to move the file starting with S to K to shut the daemon while booting. You need to see the man pages for running daemon. You also need to search the S file which is running these

Re: Autorun, alarm daemon and history (command line history)

2002-02-05 Thread Devon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At boot, after load, my KDE tool bar indicates 3 processes (?) running: -Autorun If the autorun desktop entry is empty, I don't think it causes anything to run at all. I deleted the desktop entry here. -alarm daemon Click the icon on the

Re: Autorun, alarm daemon and history (command line history)

2002-02-05 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Devon wrote: Click the icon on the right hand side of the taskbar that looks like a calendar. Select settings - configure KOrganizer, and deselect the checkbox that says Automatically start Alarm Dameon on login Good heavens, this is starting to

Re: Autorun, alarm daemon and history (command line history)

2002-02-05 Thread Devon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 06 February 2002 12:37 am, David Talkington wrote: Devon wrote: Click the icon on the right hand side of the taskbar that looks like a calendar. Select settings - configure KOrganizer, and deselect the checkbox that says

Command line history

2000-06-05 Thread Ragnar Wiencke
Hi there. Is there any way to clear the command line history? And if, has it to be done for each terminal or user? Thanks and regards, Ragnar W. [EMAIL PROTECTED] Get Your Private, Free E-mail from MSN Hotmail at http

RE: Command line history

2000-06-05 Thread Uncle Meat
On 05-Jun-2000 Ragnar Wiencke opined: Hi there. Is there any way to clear the command line history? And if, has it to be done for each terminal or user? ~/.bash_history Needs to be erased for each user. Sometimes some errant files end up at the top (/) and contain history created by root