04-11-2008
In the mid 90s I had (and still have at home) a HP 715 workstation.
after a heavy corruption due to power shortage I had a backups PSU to connect to (just for the AC) but no one would pay for more...
So I tried to figure out a workaround, after working out I had 10 minutes to shutdown the station, I came up writing a script for the cron which pinged my pc every 4 minutes and in case of a failure would do a shutdown... Not as elegant as a real software and port connection, but better than nothing...
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am a newbie and I just got a Sun Ultra 5, and want an UPS. I have been looking at the different models, but I do not know which brand has software that is compatable with Solaris 2.8 for automatic shutdown. I have looked at the power setup options in Solaris, but there doesn't seem to be any... (1 Reply)
Discussion started by: jeremiebarber
1 Replies
2. UNIX for Advanced & Expert Users
Hello Everyone I run 4 HP 9000 servers with HP-UX 11.0 on all 4, with an Infomix Database. About 6 months ago one system starting acting real weird it will display the message that it lost power (which did not) and it would shutdown, Then roughly 30 seconds later it would then say power has... (4 Replies)
Discussion started by: JackieRyan26
4 Replies
3. Solaris
I'm having some trouble getting my ups to work on my Sun ultra enterprise servers. I have it hooked to serial port b and i have the tripplite power alert software installed and running, but it doesn't see the connection, is there something else i'm supposed to do to make it realize it is hooked to... (2 Replies)
Discussion started by: kymberm
2 Replies
4. Solaris
Dear All,
I have installed package ups reillo in solaris but i could not use setup normaly, i could not connection with ttya , i need connect with ups for set system shutdown and another configuration. please i need help for solution
thanks. (0 Replies)
Discussion started by: athurbayunata
0 Replies
5. What is on Your Mind?
This thread reminded me of a couple of screwups made by an operator in my old job. The ops used to run OS backups through a script which asked for the path to the tape (/dev/rmt/whatnot). We (the sysadmins) would give these to the ops if a new server was added or the h/w path changed. One Sunday... (4 Replies)
Discussion started by: blowtorch
4 Replies
6. HP-UX
Hello everybody,
I've received yesterday a very old HP server: HP9000, A3579A, D380/2 with two 180 MHz PA-RISC CPUs, 256 MB RAM. Actual firmware is 38.40.
But no hard drives. I'm looking for 18 or 36 GB HD references.
Is 11i v3 HP-UX working on it? Or, what is the latest version? Is 256 MB... (4 Replies)
Discussion started by: Citroen
4 Replies
7. Hardware
Is anyone here using this brand, and if so, how satisfied are you with its 'PowerPanel for Linux' software? Any problems? (0 Replies)
Discussion started by: Varsel
0 Replies
8. What is on Your Mind?
Admins...
I just lerve the pop-ups that appear whilst replying to someones post.
It reminds me of "Paperclip" from my MS Windows days... ;oDD
Love it, as it makes me smile, telling me I am creating a thread ATM... ;o)
Neat little addition/feature guys... (4 Replies)
Discussion started by: wisecracker
4 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)
DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)