tag:blogger.com,1999:blog-29555375185392037752024-03-08T06:53:14.466-08:00annnonunUMMA MUM MAMMABI WAhttp://www.blogger.com/profile/09265480077758343020noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2955537518539203775.post-21494351260570779902015-04-03T03:03:00.000-07:002015-04-03T03:03:02.235-07:00I got Solaris 11.2 working on my Asrock C2550d4i board.<br />
<br />
My m1015 pcie sas-card did not show disks using the format-command. It is flashed into IT mode. However, using scanpci it was shown as:<br />
<br />
LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]<br />
<br />
I was able to connect 7 disks to the onboard sata-connectors:<br />
<br />
Searching for disks...done<br />
<br />
<br />
AVAILABLE DISK SELECTIONS:<br />
0. c2t0d0 <ata-intel ssdsa2cw12-0302-111.79gb=""></ata-intel><br />
/pci@0,0/pci1849,1f32@18/disk@0,0<br />
1. c2t1d0 <ata-intel ssdsc2ct12-300i-111.79gb=""></ata-intel><br />
/pci@0,0/pci1849,1f32@18/disk@1,0<br />
2. c4t0d0 <ata-toshiba dt01aca3-abb0-2.73tb=""></ata-toshiba><br />
/pci@0,0/pci1849,1f22@17/disk@0,0<br />
3. c4t1d0 <ata-st3000dm001-1ch1-cc24-2 .73tb=""></ata-st3000dm001-1ch1-cc24-2><br />
/pci@0,0/pci1849,1f22@17/disk@1,0<br />
4. c4t2d0 <ata-st3000dm001-1ch1-cc24-2 .73tb=""></ata-st3000dm001-1ch1-cc24-2><br />
/pci@0,0/pci1849,1f22@17/disk@2,0<br />
5. c4t3d0 <ata-st3000dm001-1ch1-cc24-2 .73tb=""></ata-st3000dm001-1ch1-cc24-2><br />
/pci@0,0/pci1849,1f22@17/disk@3,0<br />
6. c5t0d0 <ata-samsung 830-3b1q-119.24gb="" ssd=""></ata-samsung><br />
/pci@0,0/pci8086,1f12@3/pci10b5,8608@0/pci10b5,8608@1/pci1849,9172@0/disk@0,0<br />
<br />
Zfs scrubbing pefromance was not limited by the CPU. I got about 550MBps from the above setup of 3 pools.<br />
<br />
<br />
<br />
<br />
<br />UMMA MUM MAMMABI WAhttp://www.blogger.com/profile/09265480077758343020noreply@blogger.com0tag:blogger.com,1999:blog-2955537518539203775.post-34957912004329719202010-08-02T16:29:00.000-07:002010-08-02T16:39:39.253-07:00How to lock / timeout / logout an idling session in bash/screen or close an idling ssh-connection<span style="font-size:130%;">SSH</span> <br />If you wish to close idling ssh-connections you may do so by just adding two lines into your sshd_config-file. The lines would be as followed:<br /><p><code><br /></p>ClientAliveInterval 10<br />ClientAliveCountMax 1<br /></code><br /><br />The ClientAliveInterval means seconds to wait before sending first ClientAliveCountMax. So, the connection will close after ClientAliveInterval*ClientAliveCountMax=10*1=10 seconds.<br /><p><span style="font-size:130%;">Bash</span><br /></p>In bash (and similar) you may define an enviroment variable TMOUT, which defines idle time in seconds after which the bash session will log out. You may do so just by typing export TMOUT=300 into your bash or putting it in your .profile-file at ~/.profile.<br /><p><code><br /></p>export TMOUT=300<br /></code><br /><p><span style="font-size:130%;">screen</span><br /></p>This I love the most. By editing your screenrc (debian: in /etc/screenrc , freebsd: in /usr/local/etc/screenrc) you can define an idle time after which your active screen will go blank and lock itself up asking for your password to continue. <br /><br /><p>So, the config goes as:<br /></p><code><br />idle 900 lockscreen<br /></code><br /><p>where the 900 defines idle time in seconds before locking the screen up.<br /></p>UMMA MUM MAMMABI WAhttp://www.blogger.com/profile/09265480077758343020noreply@blogger.com0