web-archive-net.com » NET » L » LOFLAND.NET

Total: 169

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Lofland bLOG » Adding & Removing Disks on HPUX
    U switch ioscan fnCdisk finds hardware changes and returns NO HW instead of CLAIMED Same thing would happen if anything had tried to read write the disk now use rmsf to revove the dev files for the drive If you ever need to remove a dev file don t use rm use rmsf man is your friend The example here is removing a Hitachi SAN disk ioscan will show you both the hardware address That number with the s and the dev files for the hardware disk 101 0 0 10 0 0 1 0 5 0 10 0 sdisk NO HW DEVICE HITACHI DF600F dev dsk c34t10d0 dev rdsk c34t10d0 To wipe out a piece of hardare run rmsf a dev dsk c0t8d0 The a option should cause this to also remove the dev rdsk file and it shoudln t show up in ioscan funCdisk anymore either Now ioscan will show no signs of the hardware If you don t use the a option then you have to remove both the dev dsk and the dev rdsk files individually Then ioscan will STILL see the drive disk 101 0 0 10 0 0 1 0 5 0 10 0 sdisk NO HW DEVICE HITACHI DF600F So then you must use the hardware address to remove the drive rmsf H 0 0 10 0 0 1 0 5 0 10 0 put disk back in or put in a new disk The replace example here is a local disk the new example is an EMC SAN disk ioscan fnCdisk finds hardware changes and recognizes disk again Devices physically attached to the system should automatically show up when you run ioscan without the u option as above However there are no dev files for things like disks so you can t

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/28/hpux-disk-replacement/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG » Xserver
    LoflandBLOG wp content plugins wp email notification email notification 2 3 1 php on line 372 Lofland bLOG Xserver Filed under Unix Notes on Tuesday February 28th 2006 2 25pm by Christen Server xinit for no window manager get from client or startx includes window manager in cygwin it integrates nicely with XP with CygWIn you can run C cygwin usr X11R6 bin startxwin bat without first starting Cygwin xhost

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/28/xserver/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG » Dump Man pages to Word
    net LoflandBLOG wp content plugins wp email notification email notification 2 3 1 php on line 372 Lofland bLOG Dump Man pages to Word Filed under Unix Notes on Monday February 27th 2006 4 48pm by Christen Dump text formatted man pages for all commands in usr sbin starting with mk to testmans ls 1 usr sbin mk cut d f 4 xargs l man col b testmans There are lines that appear at the top bottom of every man page You may want to use grep to eliminate these use grep SOMETEXTINLINE file to see if it gets the right thing then grep v SOMETEXTINFILE file newfile will output all lines WITHOUT that text to the new file Items to consider using to grep out extra lines Hewlett Packard Company Gets rid of page break fillers between pages on HPUX 1M 1M only want the ones with two occurences one at the end of the line b c those are at every page top also Like so grep v Hewlett Packard Company testmans testmans1 grep v 1M 1M testmans1 testmans Or put them onto one line if you are confident grep v Hewlett Packard Company testmans grep v 1M 1M testmans1 rm testmans Open the file in winword and accept Windows Default as the Text encoding Knock your top bottom margins down to the minimum Adjusting the left right margins will likely make no difference so don t bother For very small jobs you could leave top and bottom if you like I m usually working close to 100 page though Replace p p p with p Do this repeatedly The first time the page count may cut in half After that you ll get diminishing returns Keep doing it until you either get 0 replacements or the same

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/27/dump-man-pages-to-word/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG » HPUX ServiceGuard Cluster Manager
    Failback settings If they all say manual then you are in good shape because a package will not move back to its primary node without manual intervention It is possible to use cmmodpkg to tell the packages that they may not move to a given node which would help you in this case See the man page for cmmodpkg Before doing anything crazy you should do a cmviewcl and a cmviewcl v and copy down the info That way you can see how things were set up before When you are done do a cmviewcl v and make sure PKG SWITCH is enabled for all packages It is possible for the cmhaltpkg to disable this on some of them and for you to forget to put it back Here are some tests These should come back with nothing cmviewcl v grep disabled cmviewcl v grep down These should come back with everything cmview v grep enabled cmview v grep up Check to see that everyone is running on their primary server cmviewcl v grep Primary Run cmview v through MORE also and just look to see that it all looks right You should find out from application contact what order the package should go down and up in 99 9 of the time the order does NOT matter Common sense says the come up 1 2 3 and go down 3 2 1 On this box pkgftp can go down anytime and pkg01 05 go down in reverse and up in order cmviewcl CLUSTER STATUS clustername cl5 up NODE STATUS STATE server1 up running PACKAGE STATUS STATE PKG SWITCH NODE pkg01 up running enabled server1 pkg02 up running enabled server1 pkg03 up running enabled server1 pkg04 up running enabled server1 pkg05 up running enabled server1 pkgftp1 up running enabled server1 NODE STATUS STATE server2 up running PACKAGE STATUS STATE PKG SWITCH NODE pkg06 up running enabled server2 pkg07 up running enabled server2 pkg08 up running enabled server2 pkg09 up running enabled server2 pkg10 up running enabled server2 pkgftp2 up running enabled server2 So as root from any member of the cluster I suggest that you do a cmviewcl between these commands periodically to make sure that what you expect to happen is actually happening cmhaltpkg pkgftp1 cmrunpkg n server2 pkgftp1 better to do it this way than just downing the node unless you really feel cool in which case you could technially just do a cmhaltcl server1 and all packages should move over to server 2 automatically See the man page cmhaltpkg pkg05 cmrunpkg n server2 pkg05 cmhaltpkg pkg04 cmrunpkg n server2 pkg04 cmhaltpkg pkg03 cmrunpkg n server2 pkg03 you can t hardly mess up these commands they will complain if you tell it to do the wrong thing cmhaltpkg pkg02 cmrunpkg n server2 pkg02 cmhaltpkg pkg01 cmrunpkg n server2 pkg01 Some boxes can take 30 minutes per package Some boxes take 45 minutes to move stuff over The command will hang there until it is done moving the package

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/27/hpux-serviceguard-cluster-manager/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG » Cheat Sheet
    372 Lofland bLOG Cheat Sheet Filed under Unix Notes on Monday February 27th 2006 3 51pm by Christen This is common stuff that I always forget at the wrong moment so I print this and put it on my wall at work shell To see what shell you are using being in just sh explains a lot echo SHELL Make vi your command line editory set o vi Or if you are still in sh to switch to ksh and set vi as the command line editor ksh o vi crontab minutes 0 59 hours 0 23 dates 1 31 months 1 12 days 0 6 command Set your backspace key to work stty erase BACKSPACE It may be you just need to switch how Putty is set up Set CTRL Z to suspend job stty susp Z Set other Terminal parameters stty rows 80 stty cols 25 export DISPLAY vt100 Command line completion HPX ESC or ESC ESC SUN ESC AIX ESC ABOVE ESC List all options ESC Put all options on command line LNX TAB vi h left j up k down l right i insert a append A append at end of line x delete X backspace 0 start of line or is it end of line b back word w forward word CTRL H backspace search n next instance Other handy vi commands g go to line of file G last line of file o open a line below me to type in O open a line above me to type in u undo 1 s 4 john g from first line to last line of file search for 4 and replace with john globally all instances on the line yy yank the line copy dd cut current line p paste below P Paste above x

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/27/cheat-sheet/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG » Kill Usage
    under Unix Notes on Monday February 20th 2006 9 38am by Christen kill HUP PID kill TERM PID kill KILL PID I did not write this I just found it and posted it here for my own reference Why does everyone jump straight to 9 DO NOT USE 9 AS YOUR FIRST KILL SIGNAL Try a nice friendly HUP perhaps a little stronger TERM If for some reason these don t work knock a little louder with KILL ie 9 but don t whine if something else gets hosed due to the strong signal not to scare anyone it s unlikely that anything critical is happening anyway any more than just writing a file but you could leave resources locked in use ie memory etc Also use HUP and TERM and KILL you ll be thankful when you miss your kill 1 and do a kill 1 instead you ll use HUP from then on well maybe not on a pda but on a production server etc UNIX kill signals Signal Name Signal Number Action HUP 1 Hangup INT 2 Interrupt QUIT 3 Quit dumps core file ILL 4 Illegal instruction dumps core file TRAP 5 Breakpoint trap dumps core file IOT 6 I O trap dumps core file EMT 7 Emulator trap dumps core file FPE 8 Floating Point Exception dumps core file KILL 9 Kill with extreme prejudice BUS 10 Bus error dumps core file SEGV 11 Segment Violation dumps core file SYS 12 Bad system call argument dumps core file PIPE 13 Write to nonexistent pipe ALRM 14 Alarm clock timeout TERM 15 Terminate USR1 16 User defined signal USR2 17 User defined signal CHLD 18 Child status aka CLD PWR 19 Power failure or restart WINCH 20 Window size change URG 21 Urgent socket condition IO

    Original URL path: http://www.lofland.net/LoflandBLOG/2006/02/20/kill-usage/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG ‹ Log In
    Lofland bLOG Username or Email Password Remember Me Lost your password Back to Lofland bLOG

    Original URL path: http://www.lofland.net/LoflandBLOG/wp-login.php?redirect_to=http://www.lofland.net/LoflandBLOG/2008/03/31/be-silent-keep-your-forked-tongue-behind-your-teeth-i-did-not-pass-through-death-and-fire-to-banter-words-with-a-witless-worm-gandalf/ (2016-04-27)
    Open archived version from archive

  • Lofland bLOG ‹ Lost Password
    Lofland bLOG Please enter your username or email address You will receive a link to create a new password via email Username or Email Log in Back to Lofland bLOG

    Original URL path: http://www.lofland.net/LoflandBLOG/wp-login.php?action=lostpassword (2016-04-27)
    Open archived version from archive