05-25-2011
I don't know, it looks fine to me now. Maybe you didn't reboot after patching the system ?
It looks fine now
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have problem detecting my tape drive.
In SAM, once I click on the either Automated Backups or Interactive Backup and Recovery icon, the screen will prompt searching for device and ..... nothing appears in the list.
In the end, I have the kill the SAM process and reboot the system and... (1 Reply)
Discussion started by: jennifer
1 Replies
2. UNIX for Dummies Questions & Answers
Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies
3. UNIX for Advanced & Expert Users
Hi,
1- how can I find my tape device on my server ?
2-I have a backup of a data base distributed on several file system. How using tar -x can I extract from tape to each apropriate file system ? For exemple the data base was on /d1 ; /d2 ; and /d3. Now I cd to which /dn and use tar -xvf /dev/nm0... (0 Replies)
Discussion started by: big123456
0 Replies
4. Solaris
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Discussion started by: spacewalker
4 Replies
5. UNIX for Dummies Questions & Answers
I disconected external device which was configured as rmt0. When I connect it again and run cfgmgr device name has changed (internal drive which was rmt1 is now rmt0 and external drive was rmt0 and is rmt1) and I dont know how to back it out. The thing is that for all backups I use new modell... (2 Replies)
Discussion started by: fraydey
2 Replies
6. HP-UX
Hi,
We've been having problems with our NetWorker Silo servers (running HP-UX) concerning the tape device files under /dev/rmt. For some reason they are constantly being removed/recreated (up to a couple of times per hour):
crw-rw-rw- 1 bin bin 205 0x240300 Apr 5 19:07... (1 Reply)
Discussion started by: piper28
1 Replies
7. AIX
Hi All,
After (by accident) closing a session that ran a restore command I can not access the tape drive anymore.
I get the following error:
# tctl -f /dev/rmt0 rewind
/dev/rmt0: Resource temporarily unavailable
But I cannot find any processes associated with the tape device:
# ps... (2 Replies)
Discussion started by: petervg
2 Replies
8. AIX
Hi all
The situation is as follows:
We need to take an mksysb image from an AIX 6.1 server. From some reason (irrelevant to this discussion) this server does not have access to a local CD-ROM or a tape drive. We do have another server with AIX 6.1 (but different technology level) which got access... (1 Reply)
Discussion started by: abohmeed
1 Replies
9. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
10. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
LEARN ABOUT REDHAT
reboot
HALT(8) Linux System Administrator's Manual HALT(8)
NAME
halt, reboot, poweroff - stop the system.
SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h]
/sbin/reboot [-n] [-w] [-d] [-f] [-i]
/sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h]
DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or poweroff
the system.
If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked
instead (with the -h or -r flag). For more info see the shutdown(8) manpage.
The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run.
OPTIONS
-n Don't sync before reboot or halt.
-w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file).
-d Don't write the wtmp record. The -n flag implies -d.
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-h Put all harddrives on the system in standby mode just before halt or poweroff.
-p When halting the system, do a poweroff. This is the default when halt is called as poweroff.
DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'.
NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if
the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when
/var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to
do a hard halt or reboot.
The -h flag puts all harddisks in standby mode just before halt or poweroff. Right now this is only implemented for IDE drives. A side
effect of putting the drive in standby mode is that the write cache on the disk is flushed. This is important for IDE drives, since the
kernel doesn't flush the write-cache itself before poweroff.
The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is
called or the -h switch will do nothing.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO
shutdown(8), init(8)
Nov 6, 2001 HALT(8)