Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to recover .bash_history? Post 302826721 by hergp on Thursday 27th of June 2013 07:38:12 AM
Old 06-27-2013
Restore the file from backup.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

.bash_history

Question for all sysadmins. How do you keep track of what commands each user uses on his account. I thought an easy way is to monitor .bash_history, however those files can be "edited" by the user. Is there a permission combination that will allow the shell to record to it but yet they can't edit... (12 Replies)
Discussion started by: jason6792
12 Replies

2. UNIX for Dummies Questions & Answers

Change .bash_history to another one

we need the help to change .bash_histroy file in root ,(i.e) we want to save the histroy for .temp.txt for permenently. how to do?? Help us (1 Reply)
Discussion started by: thakshina
1 Replies

3. UNIX for Advanced & Expert Users

.bash_history

During the course of the session before I logout I see some of the commands listed from my previous session but not from my current session and after I logout and log back in I see the commands which I ran before logging out. Does the .bash_history stay in the buffer or someplace else then? ... (2 Replies)
Discussion started by: jacki
2 Replies

4. Solaris

recover after delete using rm -rf

Dears, hi all i write this command rm -rf /export/home/john this there any command make me able to restore this folder again (5 Replies)
Discussion started by: jenovaux
5 Replies

5. Shell Programming and Scripting

.bash_history

Dear All, I am creating users on our servers. the .bash_history supposed to store all the commands entered by the user. My question is, how can I prevent the user himself from editing or viewing this file? I have tried chaning the owner of the .bash_history to be the root user but... (5 Replies)
Discussion started by: charbel.n.s
5 Replies

6. UNIX for Advanced & Expert Users

.bash_history modification

Hi Experts, I know my question would be strange but i need to understand how the .bash_history file is logging user actions (the mechanism) and if possible modify it to include also the date/time of every action done by the user. Sample file: # more .bash_history ssh <IP address> -l axadmin... (3 Replies)
Discussion started by: Dendany83
3 Replies

7. UNIX for Dummies Questions & Answers

how to store time in .bash_history file

Hi - user commands are written in . bash_history of that user when he logs out. my bash_history file shows. not sure what that number means #1329618972 ls -la #1329618978 ls #1329618980 ls -la my bash_profile looks like this PATH=$PATH:$HOME/bin export PATH export... (3 Replies)
Discussion started by: oraclermanpt
3 Replies

8. Shell Programming and Scripting

Display .bash_history with timestamp using script

Hi would like to ask if there is anyway to display .bash_history with timestamp using shell script? i know that you should use history command with HISTTIMEFORMAT="%d/%m/%y %T " to display it in terminal but it does not work when i use it on shell script. It seem that you can't run history... (1 Reply)
Discussion started by: pikamon
1 Replies

9. Solaris

Recover rm command

Consider a situation where in you have used rm command wrongly in a particular directory say rm -r * and we don't have any backup of those files which ever are deleted. NOTE: I'm not facing situation like this but wanted to know what all options are available for such a situation. is... (5 Replies)
Discussion started by: Gautham
5 Replies

10. UNIX for Beginners Questions & Answers

How to get the "history" command to show all that is in the .bash_history file?

I am using the bash shell. When I view my recent command history using the "history" command from the prompt, it only shows me the commands starting at #928. The commands I need are earlier than that, but I can't figure out how to make the other 927 display. They are in my .bash_history... (1 Reply)
Discussion started by: Twinklefingers
1 Replies
BACKUP_JOBS(8)						       AFS Command Reference						    BACKUP_JOBS(8)

NAME
       backup_jobs - Lists pending and running operations in interactive mode

SYNOPSIS
       jobs [-help]

       j [-h]

DESCRIPTION
       The backup jobs command lists the job ID number and status of each backup operation running or pending in the current interactive session.

       This command can be issued in interactive mode only. If the issuer of the backup interactive command included the -localauth flag, the
       -cell argument, or both, those settings apply to this command also.

       To terminate operations that appear in the output, issue the backup kill command and identify the operation to cancel with the job ID
       number from this command's output.

       To check the status of a Tape Coordinator, rather than of a certain operation, use the backup status command.

OPTIONS
       -help
	   Prints the online help for this command. All other valid options are ignored.

OUTPUT
       The output always includes the expiration date and time of the tokens that the backup command interpreter is using during the current
       interactive session, in the following format:

	  <date>   <time>: TOKEN EXPIRATION

       If the execution date and time specified for a scheduled dump operation is later than <date time>, then its individual line (as described
       in the following paragraphs) appears below this line to indicate that the current tokens will not be available to it.

       If the issuer of the backup command included the -localauth flag when entering interactive mode, the line instead reads as follows:

	  :  TOKEN NEVER EXPIRES

       The entry for a scheduled dump operation has the following format:

	  Job <job_ID>:  <timestamp>:  dump  <volume_set>  <dump_level>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <timestamp>
	   Indicates the date and time the dump operation is to begin, in the format month/date/year hours:minutes (in 24-hour format)

       <volume_set>
	   Indicates the volume set to dump.

       <dump_level>
	   Indicates the dump level at which to perform the dump operation.

       The line for a pending or running operation of any other type has the following format:

	  Job <job_ID>:  <operation>  <status>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <operation>
	   Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command:

	   Dump (dump name)
	       Initiated by the backup dump command. The dump name has the following format:

		   <volume_set_name>.<dump_level_name>

	   Restore
	       Initiated by the backup diskrestore, backup volrestore, or backup volsetrestore command.

	   Labeltape (tape_label)
	       Initiated by the backup labeltapen command. The tape_label is the name specified by the backup labeltape command's -name or -pname
	       argument.

	   Scantape
	       Initiated by the backup scantape command.

	   SaveDb
	       Initiated by the backup savedb command.

	   RestoreDb
	       Initiated by the backup restoredb command.

       <status>
	   Indicates the job's current status in one of the following messages. If no message appears, the job is either still pending or has
	   finished.

	   number Kbytes, volume volume_name
	       For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume
	       currently being dumped.

	   number Kbytes, restore.volume
	       For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far.

	   [abort requested]
	       The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator.

	   [abort sent]
	       The operation is canceled by the backup kill command.  Once the Backup System removes an operation from the queue or stops it from
	       running, it no longer appears at all in the output from the command.

	   [butc contact lost]
	       The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling
	       the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out.

	   [done]
	       The Tape Coordinator has finished the operation.

	   [drive wait]
	       The operation is waiting for the specified tape drive to become free.

	   [operator wait]
	       The Tape Coordinator is waiting for the backup operator to insert a tape in the drive.

EXAMPLES
       The following example shows that two restore operations and one dump operation are running (presumably on different Tape Coordinators) and
       that the backup command interpreter's tokens expire on 22 April 1999 at 10:45 am:

	  backup> jobs
	  Job 1: Restore, 1306 Kbytes, restore.volume
	  Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
	  Job 3: Restore, 2498 Kbytes, restore.volume
		 04/22/1999 10:45: TOKEN EXPIRATION

PRIVILEGE REQUIRED
       None. However, queuing any operation requires privilege, and it is possible to issue this command only within the interactive session in
       which the jobs are queued.

SEE ALSO
       backup(8), backup_interactive(8), backup_kill(8), backup_quit(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							    BACKUP_JOBS(8)
All times are GMT -4. The time now is 07:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy