Bricks of the knowledge wall

GUDS is what Oracle can ask you

2011-01-09T06:30:00.003+02:00

GUDS

When working with vendor on performance issue, this tool will be required.

Be careful don't run it during business hours, performance degradation will go.

Guds is a script to gather performance stats for Solaris.
Sample usage is
./guds_2.4.5
./guds_2.4.5 -qX -H3 -s65040465

-qX is for quite mode
-H3 is for running it for 3 hours
-sNNNNN is the sun case number (info embeded in dirs created by guds to
store the files).

It collects lots of info in /var/tmp/CASEID/guds-DATE-TIME/…

SLAMD!

2010-08-26T12:55:00.004+02:00

The very good performance testing engine:
SLAMD Distributed Load Generation Engine

Default and permited projects

2010-08-26T12:25:00.005+02:00

If you want to assign default project to a user, then use
usermod -K project=projname username

If want to give permission(newtask -p projname) to use but not to make the default one, then
projmod -U username projectname

The cruel trooth abou fssnap

2010-08-25T13:55:00.004+02:00

There are two fssnap in Solaris with pretty the same features(don't know the historical background of this separation)
/usr/sbin/fssnap and /usr/lib/fs/ufs/fssnap !
The difference is that the second one shows more detailed information :

$/usr/sbin/fssnap -i /usr
0 /usr

$/usr/lib/fs/ufs/fssnap -i /usr
Snapshot number : 0
Block Device : /dev/fssnap/0
Raw Device : /dev/rfssnap/0
Mount point : /usr
Device state : idle
Backing store path : /export/snapshots/snapshot0
Backing store size : 864 KB
Maximum backing store size : Unlimited
Snapshot create time : Mon Aug 23 22:50:06 2010
Copy-on-write granularity : 32 KB

Simplest iscsi configuration in a minute

2010-08-23T14:56:00.002+02:00

Work with iSCSI devices is really easy and comfortable in Solaris 10, consider following steps to create and use the simplest configuration:
On target.

Declare base directory
iscsitadm modify admin -d /export/sandbox
Create the target
iscsitadm create target --size 10m sandbox
List created target and copy iqn
iscsitadm list target

On initiator.
Use the target
iscsiadm add static-config iqn.1986-03.com.sun:02:a5a27478-ded0-c8c3-9c71-a882cbfbc0ed.sandbox, ip-address

Label the disk:
#format

Useful:
The command shows relation of ISCSI LUN and local device name
iscsiadm list target -S

Sun Java Console Timeout

2010-07-29T15:06:00.003+02:00

If you often get hot because of console timeout log offs - here we are!

# wcadmin add -p -a console session.timeout.value=5

Don't waste pure man's RAM

2010-07-29T15:01:00.003+02:00

Want extra 200MB of RAM on Solaris Vmware Guest - disable Java Console, if you don't use it of course :)

#svcadm disable webconsole

Bluetooth gprs internet in several steps.

2010-07-13T19:57:00.002+02:00

The proposed way doesn't pretend to be the most convenient but it at least works :)

So,

1.Enable bluetooth on the phone.
2.Discover it's MAC address:
$hcitool scan
3.Find out which channel is used for «Dial UP networking» on your phone:
$sdptool browse 00:21:AA:8E:E1:00
4.Bind rfcomm device to discovered channel:
rfcomm bind 0 00:21:AA:8E:E1:00 2
5.Now we can use /dev/rfcomm0 in pppd configuration.
6.Use pppconf to create ppp configuration for your operator, I'll show mine at the end of the tip.
7.Use pon xl.kyivstar.net to connect
Actually I ,also, thing that there must be an easier way , let me know if you'll find one!

cat /etc/ppp/peers/xl.kyivstar.net:

# This optionfile was generated by pppconfig 2.3.18.

#

#

hide-password

noauth

connect "/usr/sbin/chat -v -f /etc/chatscripts/xl.kyivstar.net"

debug

/dev/rfcomm0

115200

defaultroute

noipdefault

user "none"

ipparam xl.kyivstar.net

usepeerdns

nopcomp

novj

novjccomp

nobsdcomp

nodeflate

noaccomp

cat /etc/chatscripts/xl.kyivstar.net:

TIMEOUT 35

ECHO ON

ABORT '\nBUSY\r'

ABORT '\nERROR\r'

ABORT '\nNO ANSWER\r'

ABORT '\nNO CARRIER\r'

ABORT '\nNO DIALTONE\r'

ABORT '\nRINGING\r\n\r\nRINGING\r'

'' \rAT

'OK' 'AT+CGDCONT=1,\"IP\",\"xl.kyivstar.net\"'

'OK' ATD*99***1#

CONNECT

Check content of the IPS packages

2010-03-29T15:28:00.001+02:00

$pkg contents -r tcl-sqlite-3
PATH
usr
usr/lib
usr/lib/tcl8.4
usr/lib/tcl8.4/sqlite3
usr/lib/tcl8.4/sqlite3/32
usr/lib/tcl8.4/sqlite3/64
usr/lib/tcl8.4/sqlite3/amd64
usr/lib/tcl8.4/sqlite3/amd64/libtclsqlite3.so
usr/lib/tcl8.4/sqlite3/libtclsqlite3.so
usr/lib/tcl8.4/sqlite3/pkgIndex.tcl

If the target is a meta-package:

$pkg contents -rm ruby-dev
set name=fmri value=pkg:/ruby-dev@0.5.11,5.11-0.111:20090508T235714Z
set name=variant.opensolaris.zone value=global value=nonglobal
set name=description value="Ruby Development cluster"
set name=info.classification value=org.opensolaris.category.2008:Development/Ruby
set name=variant.arch value=sparc value=i386
set name=publisher value=opensolaris.org
depend fmri=SUNWj6dev@0.5.11-0.111 type=require
depend fmri=SUNWj6man@0.5.11-0.111 type=require
depend fmri=SUNWj6cfg@0.5.11-0.111 type=require
depend fmri=SUNWj6rt@0.5.11-0.111 type=require
depend fmri=SUNWcvs@1.12.13-0.111 type=require
depend fmri=SUNWfirefox@0.5.11-0.111 type=require
depend fmri=netbeans@6.5.1-0.111 type=require
depend fmri=SUNWruby18@1.8.7.72-0.111 type=require
depend fmri=SUNWj6dmo@0.5.11-0.111 type=require
depend fmri=SUNWsvn@1.4.3-0.111 type=require
depend fmri=SUNWj6dvx@0.5.11-0.111 type=require
depend fmri=SUNWj6dmx@0.5.11-0.111 type=require
depend fmri=SUNWmercurial@1.1.2-0.111 type=require
depend fmri=SUNWj6rtx@0.5.11-0.111 type=require
depend fmri=SUNWsquid@2.7.6-0.111 type=require
depend fmri=SUNWmemcached@1.2.5-0.111 type=require

Grub difference

2010-03-17T14:03:00.003+02:00

In Solaris grub is shipped with additional commands which make life easier:
installgrub - install GRUB in a disk partition or a floppy
bootadm - manage bootability of GRUB-enabled operating sys-tem

Beadm usage examples

2010-03-16T14:08:00.002+02:00

beadm list -[sda]

note: /boot/grub/menu.lst - doesn't exist by default, it's created when "beadm create" is executed.

beadm create beName
beadm mount beName mountpoint
beadm activate beName

Create BE from snapshot or another inactive BE:
beadm create -e non-activeBeName beName

Create a Snapshot of a Boot Environment:
beadm create BEname@snapshotdescription

You can patch BE or install packages into it:
pkg -R /mnt image-update
pkg -R /mnt install packagename

To destroy a boot environment, type the following:
beadm destroy beName

Use the following command to rename the boot environment:
beadm rename beName newBeName

SMF Contracts or how to find out what FMRI the process uses

2010-03-11T14:16:00.001+02:00

The SMF uses the contracts to monitor the processes of a service.

Based on this events SMF can take action to react on this events. Per default, SMF

stops and restart a service, when any member of the contract dumps core, gets a signal

or dies due a hardware failure. Additionally the SMF does the same, when theres no

member process left in the contract.

We can use contracts to find out what SMF services have started processes which belongs to these contracts.

# ptree -c `pgrep sendmail `

[ process contract 1]

1 / sbin / init

[ process contract 4]

7 /lib/svc/bin/svc. startd

[ process contract 103]

776 /usr/lib/ sendmail -bd -q15m -C /etc/ mail / local .

777 /usr/lib/ sendmail -Ac -q15m

#ctstat -vi 90

CTID ZONEID TYPE STATE HOLDER EVENTS QTIME NTIME

90 0 process owned 7 0 - -

cookie: 0x20

informative event set: none

critical event set: hwerr empty

fatal event set: none

parameter set: inherit regent

member processes: 523

inherited contracts: none

service fmri: svc:/network/smtp:sendmail

service fmri ctid: 90

creator: svc.startd

aux: start

#ctwatch 90 – you can monitor what happens to the contract

Solaris memory measurement

2010-03-09T12:59:00.002+02:00

Memory measuring tricks:

Total Physical Memory:
# prtconf

Kernel Memory:
# sar -k 1 1

Free Memory:
Ignore the first line it's general information.
# vmstat 3 - consider that each memory allocation assumes similar size swap reservation

Two indicators of a RAM shortage are the scan rate and swap device activity.

Scan Rate:
sar -g or vmstat(sr)

Paging:
Vmstat(po)

Swap Device Activity:
iostat -x
vmstat
sar -d
If there are I/O's queued for the swap device, application paging is occurring.

Process Memory Usage:
Ps -ly ,prstat, top
Pmap -x PID
ipcs -mb - shared memory usage

Swap space:
swap -l reports total and free space for each of the swap partitions or files that are available to the system
swap -s reports the total available amount of virtual memory
sar -r

Watching Sun Cluster's binary logs

2010-03-08T16:08:00.003+02:00

To be able analyze sun cluster behavior the usefull tool to have is showev4
./showev4 /var/cluster/logs/eventlog

You can get it here
http://www.unixpin.com/wordpress/wp-content/uploads/2008/06/showev4.zip

Jumpstart boot process

2010-03-04T15:41:00.002+02:00

These tip doesn't explain Jumpstart process from "A" to "Z", I've just outlined some useful passages.

Boot process during jumpstart.
1. Client sends a RARP for its IP address
2. The Boot Server responds via RARPD (in.rarpd) with the IP address in /etc/ethers or the ethers NIS/NIS+ map depending on the ethers setting in /etc/nsswitch.conf
3. The client sends a tftp request for a bootimage
4. The server starts in.tftp from inetd and sends the small net kernel image
5. The client then sends out a bootp request
6. The server responds with the clients entry from /etc/bootparams
7. The client NFS mount it's root partition from the install server
8. The client then mounts the configuration server (/jumpstart) and runs "sysidtool".
9. It then mounts the install image and runs Suninstall to begin the install process.

Snoop Output

1 0.00000 OLD-BROADCAST -> (broadcast) RARP C Who is 0:a0:24:d2:f6:34 ?
2 3.00626 pikachu -> togepi RARP R 0:a0:24:d2:f6:34 is 192.168.0.12, togepi
3 0.00078 togepi -> BROADCAST BPARAM C WHOAMI? 192.168.0.12
4 0.00862 pikachu -> togepi BPARAM R WHOAMI? togepi in\
5 0.00054 togepi -> (broadcast) ARP C Who is 192.168.0.1, 192.168.0.1 ?
6 0.00006 192.168.0.1 -> togepi ARP R 192.168.0.1, 192.168.0.1 is 0:90:27:d0:fd:27
7 0.00037 togepi -> pikachu BPARAM C GETFILE root
8 0.00163 pikachu -> togepi BPARAM R GETFILE File=/export/install/2.6/x86/Solaris_2.6/Tools/Boot
9 0.00073 togepi -> pikachu PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP
10 0.00122 pikachu -> togepi PORTMAP R GETPORT port=32774
11 0.00075 togepi -> pikachu MOUNT1 C Mount /export/install/2.6/x86/Solaris_2.6/Tools/Boot
12 0.00281 pikachu -> togepi MOUNT1 R Mount OK FH=CE64
13 0.01728 togepi -> pikachu NFS C LOOKUP2 FH=CE64 etc
14 0.00099 pikachu -> togepi NFS R LOOKUP2 OK FH=8298
15 0.00066 togepi -> pikachu NFS C LOOKUP2 FH=8298 bootrc
16 0.00040 pikachu -> togepi NFS R LOOKUP2 OK FH=6C1F
17 0.00068 togepi -> pikachu NFS C GETATTR2 FH=6C1F
18 0.00038 pikachu -> togepi NFS R GETATTR2 OK
19 0.00075 togepi -> pikachu NFS C GETATTR2 FH=6C1F
20 0.00034 pikachu -> togepi NFS R GETATTR2 OK
21 0.00086 togepi -> pikachu NFS C READ2 FH=6C1F at 0 for 1344

Source: http://amorin.org/professional/jumpstart.php#

Sun Cluster Console

2010-02-19T15:16:00.006+02:00

Install Cluster console:

Mount cd with the product
cd sc32_location/Solaris_{sparc_or_x86}/Products/sun_cluster/Solaris_10/Packages
pkgadd -d . SUNWccon

Add to .profile:

PATH=$PATH:/opt/SUNWcluster/bin
MANPATH=$MANPATH:/opt/SUNWcluster/man
export PATH MANPATH

Sample /etc/clusters File:
sc-cluster pnode1 pnode2 pnode3

Define consoles /etc/serialports file
sc-node1 sc-tc 23
sc-node2 sc-tc 23

Simplest way to mount CDROM

2010-02-19T14:57:00.001+02:00

#svcadm restart volfs

Resource pool zone assignment.

2010-02-17T14:40:00.004+02:00

Pooladm -e
poolcfg -c 'create pset pset_test1 (uint pset.min = 2; uint pset.max = 10)'
poolcfg -c 'create pool testpool1'
poolcfg -c 'associate pool testpool1 (pset pset_test1)'
poolcfg -c info - shows static information based on /etc/pooladm.conf
poolcfg -dc "transfer to pset pset_test1 (cpu 0; cpu 2)"
or
poolcfg -dc 'transfer 2 from pset pset_default to pset_test1'

pooladm -c initialize from /etc/pooladm.conf

There are two way of doing this: static(requires zone restart) and dynamic.
Static:
1. zonecfg -z testzone1 set pool=testpool1
2. zoneadm -z testzone reboot

Dynamic:
poolbind -p pool_default -i zoneid 5

Users notification about subversion commits(the most scallable way).

2010-02-11T22:01:00.002+02:00

1. Get http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/mailer/mailer.py and
put into "REPO"/hooks.
2. Get http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/mailer/mailer.conf.example and put as "REPO/mailer.conf"
3. Modify mailer.conf for your needs.
4. mv "REPO"/hooks/post-commit.tmpl "REPO"/hooks/post-commit
5. Add to post-commit:
$REPOS"/hooks/mailer.py commit "$REPOS" $REV "$REPOS"/mailer.conf"

How to find out what mode Solaris can use on your hardware 64 or 32?

2010-02-08T14:10:00.003+02:00

isainfo -v or isainfo -b:

64-bit amd64 applications
ssse3 cx16 sse3 sse2 sse fxsr mmx cmov amd_sysc cx8 tsc fpu
32-bit i386 applications
ssse3 cx16 sse3 sse2 sse fxsr mmx cmov sep cx8 tsc fpu

Share ZFS dataset through CIFS/Samba

2009-12-30T20:40:00.001+02:00

Prerequisites:

If you use opensolaris, install SUNWsmbsr.

1. zfs set sharesmb=on rpool/export/home

sharemgm show -vp

2. svcadm enable smb/server

stever@opensolaris:~# cat >> /etc/pam.conf

# Seem to need this line for smb / cifs:

other password required pam_smb_passwd.so.1 nowarn

(Control-D to end)

stever@opensolaris:~# passwd

passwd: Changing password for stever

New Password:

Re-enter new Password:

passwd: password successfully changed for stever

Autofs and auto mounted homes.

2009-12-30T20:35:00.002+02:00

Prerequisites:

It´s important that both hosts can resolv the hostname of the other system.

User/group ID's must be the same on all hosts.

ON FILE SERVER

1. Share directory which will be automaunted as home.

If it's on ZFS:

#zfs set sharenfs=on rpool/export/home

#sharemgm show -vp

If ufs:

#echo "share -F nfs -d \"Home Directories\" /export/home" >> /etc/dfs/dfstab

#shareall

#exportfs

2. Make rpc authorize you:

#svccfg -s svc:/network/rpc/bind

#svc:/network/rpc/bind> setprop config/local_only = false

#svc:/network/rpc/bind> quit

#svcadm refresh svc:/network/rpc/bind

cat >>/etc/hosts.allow

rpcbind: ALL

chmod 644 /etc/hosts.allow

2. Create user and their HOMES :

useradd -u 2000 -m -d /export/home/user -s /bin/bash user

ON CLIENT

1. echo "* gandalf:/export/home/&" >> /etc/auto_home

2.svcadm disable autofs;svcadm enable autofs

3. Create user the same user here if you are'nt using LDAP.

Testing configuration:

ls /net/server

Additional reading.

Cacaoadm and SUN Directory Server 6.3.1

2009-12-02T14:47:00.002+02:00

After upgrading to DS 6.3.1 on Solaris 10:
#cacaoadm status
Cannot find property: [cacao.embedded].

This can be fixed by addition of "use.j2me=false" option to
/etc/cacao/instances/default/private/cacao.properties

Configuring SMF Service Probes for Containers in Sun Cluster 3.2.

2009-11-19T14:27:00.002+02:00

Prerequsites:
Program inside a clustered zone must be managed through SMF and be in OFFLINE state.
Script for program must reside inside the zone and return 0 - normal, 100 - service restart needed, 201 - zone restart/switch is needed.

1. On clustered global zone edit file /opt/SUNWsczone/sczsmf/util/sczsmf_config:

RS=sczsmf-rs
RG=sczbt-rg
SCZBT_RS=sczbt-rs
ZONE=sczbt-zone-name
SERVICE=smf-service
RECURSIVE=true|false
STATE=true|false
SERVICE_PROBE=sczsmf-service-probe
The meaning and permitted values of the keywords in the sczsmf_config file are as
follows:
RS=sczsmf-rs
Specifies the name that you are assigning to the zone SMF resource. This must be
defined.
RG=sczbt-rg
Specifies the name of the resource group the zone boot resource resides in. This
must be defined.
SCZBT_RS=sczbt-rs
Specifies the name of the zone boot resource. You must specify a value for this
keyword.
ZONE=sczbt-zone-name
Specifies the zone name. This must be defined.
SERVICE=smf-service
Specifies the SMF service to enable/disable. This must be defined.
RECURSIVE=true|false
Specifies true to enable the service recursively or false to just enable the service
and no dependents. This must be defined.
STATE=true|false
Specifies true to wait until the service state is reached or false to not wait until
the service state is reached. This must be defined.
SERVICE_PROBE=sczsmf-service-probe
Specify the script to check the SMF service.

2. Run
/opt/SUNWsczone/sczsmf/util/sczsmf_register - to register SMF service resource within cluster.

3. Set failover properties for new resource(it may require to put resource offline):
sudo clresource set -p Failover_enabled=True sczsmf-rs
sudo clresource set -p Failover_mode=SOFT sczsmf-rs

4. Enable resource
sudo clresource enable sczsmf-rs

5. Check status:
sudo clresource status sczsmf-rs

Usefull comands:
clresourcegroup show
clresource list-prop

Additional reading:
http://docs.sun.com/app/docs/doc/819-3069/cacjgdbc?a=browse

How to find recently added FC disks

2009-11-17T10:14:00.004+02:00

Save output format and zpool status commands in order to have list of disks you already had.
cfgadm -al -o show_SCSI_LUN
devfsadm
format - you can observe all disks now

Useful comands:
stmsboot -L - mapping between multipathed and physical device
luxadm -e dump_map /dev/fc/fp0 - shows devices attached to particular FC HBA
mpathadm list mpath-support -lists drivers
mpathadm show mpath-support libmpscsi_vhci.so - shows supported features of particular driver
mpathadm list lu - shows mpath devices status
mpathadm show lu /dev/rdsk/c4t60060E801526AE00000126AE00000181d0s2 - particular mpath device configuration

Generate sshd server keys

2009-11-09T14:16:00.000+02:00

/lib/svc/method/sshd -c
svcadm refresh ssh

Turning on Sun Cluster checks debug

2009-11-03T14:17:00.001+02:00

- set debug to ALL in/opt/SUNWsczone/sczbt/etc/config
- Added daemon.debug in the syslog so it writes to /var/adm/messsages

Resetting root password on Solaris

2009-11-02T13:38:00.000+02:00

The subject can be easily performed using Solaris install CD/DVD. Just boot from it and chose "command shell", then:
#chroot /a /sbin/sh
#passwd root

Simple upgrade with Liveupgrade

2009-10-29T11:44:00.000+02:00

lucreate -c "old" -m /:/dev/dsk/c0d0s0:ufs -n "u8"
lustatus
luupgrade -u -n u8 -s /cdrom/
luactivate u8
use init 6 or shutdown to reboot server

Persistent static routes

2009-10-14T14:30:00.005+02:00

# route -p add 192.168.15.0 192.168.15.1

The static routes will be stored in file /etc/inet/static_routes.

Appeared in Solaris 10 update 3

Solaris extended accounting tips

2009-10-08T10:07:00.003+02:00

Accounting types available: Task, Process, Flow (IPQoS), and Net (Crossbow). Each accounting type has a datafile to store records in which is user defined. A variety of different resources can be tracked for each accounting type, which can either individually selected or specified as either "extended" or "basic", which are groupings of resources.

Activating:

Become superuser or assume an equivalent role.
Activate extended accounting for processes.

# acctadm -e extended -f /var/adm/exacct/proc process
Activate extended accounting for tasks.

# acctadm -e extended,mstate -f /var/adm/exacct/task task
Activate extended accounting for flows.

# acctadm -e extended -f /var/adm/exacct/flow flow
Activating on persistent basis:

# ln -s /etc/init.d/acctadm /etc/rc2.d/Snacctadm

# ln -s /etc/init.d/acctadm /etc/rc2.d/Knacctadm

Display Extended Accounting Status

$acctadm

View Available Accounting Resources

$acctadm -r

Turn off process accounting.

# acctadm -x process

Turn off task accounting.

# acctadm -x task

Turn off flow accounting.

# acctadm -x flow

Commands which use it's databases:

lastcomm
acctcom
exdump?

If you really want to take advantage of accounting data you'll need to build your own custom tools using either the Exacct PERL module (written by Sun, found in CPAN, and part of the Solaris PERL distribution) or the libexacct C library.

Good article:

http://www.cuddletech.com/blog/pivot/entry.php?id=1017

Command list for work with projects/tasks in Solaris

2009-10-07T11:19:00.004+02:00

ps -o user,pid,uid,projid,taskid,comm
id -p
pgrep -J projidlist
pkill -J projidlist
pgrep -T taskidlist
pkill -T taskidlist
prstat -J
prstat -T
projects -l
projadd -U mark -p 4113 booksite
projdel booksite
projmod -n
projects username
newtask -v -p booksite
newtask -v -p booksite -c 8100
projmod -a -K task.max-lwps myproject
projmod -a -K "task.max-lwps=(priv,100,deny)" myproject
projmod -a -K "task.max-lwps=(priv,1000,signal=KILL)" myproject
projmod -r -K "task.max-lwps=(priv,100,deny)" myproject
projmod -s -K "task.max-lwps=(priv,100,none),(priv,120,deny)" myproject
projmod -s -K task.max-lwps myproject

Use the prctl command to make runtime interrogations of and modifications to the resource
controls associated with an active process, task, or project on the system. See the prctl(1) man
page for more information.
# prctl $$ - displays all resource control values for given process.
# prctl -n process.max-file-descriptor $$ - more concrete
# prctl -n project.max-lwps -t privileged -v 3 -e deny -i project x-files - Add a new privileged value for project.max-lwps that limits the number of LWPs to three.
# prctl -n project.max-lwps -i project x-files - verifies previous.
# prctl -n process.max-file-descriptor -r -v 128 $$ - change the lowest value of the process.max-file-descriptor resource control.

Use the rctladm command to make runtime interrogations of and modifications to the global
state of the resource controls facility. See the rctladm(1M) man page for more information.
# rctladm -e syslog process.max-file-descriptor - enable the global syslog attribute of process.max-file-descriptor
# rctladm - displays the global flags, including the global type flag, for each resource control.
# ipcs - displays information regarding open IPCS
# ipcs -J - displays information regarding open IPCS (Project oriented)

Capacity Warnings.

# prctl -n task.max-lwps -v 40 -t privileged -d all ‘pgrep httpd‘
# rctladm -e syslog task.max-lwps
Observe whether the workload trips the resource control:
If it does, you will see /var/adm/messages such as:
Jan 8 10:15:15 testmachine unix: [ID 859581 kern.notice]
NOTICE: privileged rctl task.max-lwps exceeded by task 12

Rlimits and resource controls.

UNIX systems have traditionally provided a resource limit facility (rlimit,plimit,ulimit).
The resource controls facility provides compatibility interfaces for the resource limits facility.
Existing applications that use resource limits continue to run unchanged.

Solaris Resource Pools (moving cpus)

2009-10-07T09:35:00.003+02:00

Assume you have pset "test", then you can create pool.txt which contains:

#modify pset test-pset ( uint pset.min = 8; uint pset.max = 16 )
#transfer to pset test-pset ( cpu 64; cpu 65; cpu 66; cpu 67; cpu 68; cpu 69; cpu 70; cpu 71)
transfer to pset pset_default ( cpu 48; cpu 49; cpu 50; cpu 51; cpu 52; cpu 53; cpu 54; cpu 55 )
modify pset test-pset ( uint pset.min = 8; uint pset.max = 8 )
##

Then:
$sudo poolcfg -f pool.txt
$sudo pooladm -c

Sybase SMF scripts

2009-10-07T09:28:00.006+02:00

/etc/sybase_config contains:

# Sybase config

#run_user;sybase_home;config;db_user;db_pass
syb_run_user;/sybserver/sybase_instance_home;instance_name;none;none

Sybase_to_smf.sh is for creation of SMF manifests:

#!/sbin/sh

SYBASE_CONFIG=./sybase_config

if [ ! -s $SYBASE_CONFIG ] ; then
echo "The Sybase configuration-file $SYBASE_CONFIG does not exist or is empty!"
fi

for DATASERVER_ENTRY in ` grep -v "^#" $SYBASE_CONFIG ` ; do
RUN_USER=`echo $DATASERVER_ENTRY | cut -f1 -d\;`
SERVER_HOME=`echo $DATASERVER_ENTRY | cut -f2 -d\;`
CONFIG_NAME=`echo $DATASERVER_ENTRY | cut -f3 -d\;`

cat<<EOF >$CONFIG_NAME.xml
<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle type='manifest' name='export'>
<service name='database/sybase' type='service' version='0'>
<dependency name='network-service' grouping='require_all' restart_on='none' type='service'>
<service_fmri value='svc:/network/service'/>
</dependency>
<exec_method name='start' type='method' exec='/lib/svc/method/sybase start' timeout_seconds='600'>
<method_context/>
</exec_method>
<exec_method name='stop' type='method' exec='/lib/svc/method/sybase stop' timeout_seconds='3'>
<method_context/>
</exec_method>
<instance name='$CONFIG_NAME' enabled='false'>
<property_group name='vars' type='framework'>
<propval name='run_user' type='astring' value='$RUN_USER'/>
<propval name='server_home' type='astring' value='$SERVER_HOME'/>
<propval name='config_name' type='astring' value='RUN_$CONFIG_NAME'/>
<propval name='server_name' type='astring' value='$CONFIG_NAME'/>
</property_group>
</instance>
<stability value='Unstable'/>
<template>
<common_name>
<loctext xml:lang='C'>layered network services</loctext>
</common_name>
<description>
<loctext xml:lang='C'>Network infrastructure services
requiring name service availability.</loctext>
</description>
<documentation>
<manpage title='ifconfig' section='1M' manpath='/usr/share/man'/>
</documentation>
</template>
</service>
</service_bundle>
EOF

done

This one put into /lib/svc/method:

#!/sbin/sh -x

. /lib/svc/share/smf_include.sh
getproparg() {
val=`svcprop -p $1 $SMF_FMRI`
[ -n "$val" ] && echo $val
}
RUN_USER=`getproparg vars/run_user`
RUN_USER_HOME=`getproparg vars/server_home`
CONFIG_NAME=`getproparg vars/config_name`
SERVER_NAME=`getproparg vars/server_name`

STARTSERVER=$RUN_USER_HOME/system/ASE-15_0/install/startserver
STARTSERVER_CONF=$RUN_USER_HOME/cfg/$CONFIG_NAME
STOPSERVER="pkill -u $RUN_USER"

SYBASE_CONFIG=/etc/sybase_config
if [ ! -s $SYBASE_CONFIG ] ; then
echo "The Sybase configuration-file $SYBASE_CONFIG does not exist or is empty!"
fi

for DATASERVER_ENTRY in ` grep -v "^#" $SYBASE_CONFIG ` ; do
DB_USER=`echo $DATASERVER_ENTRY | cut -f4 -d\;`
DB_PASS=`echo $DATASERVER_ENTRY | cut -f5 -d\;`
done

case "$1" in
'start')
if [ -x $STARTSERVER ]; then
umask 022
su - $RUN_USER -c ".profile; $STARTSERVER -f $STARTSERVER_CONF" 2>&1
else
echo "$0: $STARTSERVER does not exist or is not executable."
fi
;;

'restart')
if [ -x $STARTSERVER ]; then
umask 022
$STOPSERVER
su - $RUN_USER -c ".profile; $STARTSERVER -f $STARTSERVER_CONF" 2>&1
else
echo "$0: $STARTSERVER does not exist or is not executable."
fi
;;

'stop')
#su - $RUN_USER -c "isql -S$SERVER_NAME -U$DB_USER -P$DB_PASS<<EOF
#shutdown syb_backup
#go
#shutdown
#go
#EOF"
su - $RUN_USER -c "printf 'shutdown syb_backup\ngo\nshutdown\ngo' |isql -S$SERVER_NAME -U$DB_USER -P$DB_PASS"
;;

*)
echo "Usage: $0 { start | stop }"
exit 1
;;

esac
exit 0

#svccfg validate file.xml
#svccfg import file.xml

The fastest way to create long term ssl certificates for SUN Directory Server 6.3

2009-10-06T18:28:00.002+02:00

If you've used Sun Directory Server you probably met the problem of self-signed certificates,
solution below will help you to resolve it in the fastest way.

# pick a new password or you can't run certutil later
$ dsadm set-flags /path/ds1 cert-pwd-prompt=on

# create a self sign cert valid for 24 months
$ serverroot/dsee6/bin/certutil -d /path/ds1/alias -P slapd- -x -S -n longlife -s cn=ldap.example.com:389,st=TX,C=US,L=Crawford -t CTu,u,u -v 24

$ serverroot/dsee6/bin/certutil -d /path/ds1/alias -P slapd- -L -n longlife | head -15
# turn off the password or you'll be prompted everytime the instance starts
$ dsadm set-flags /path/ds1 cert-pwd-prompt=off

VLV indexes creation

2009-09-28T14:14:00.004+02:00

Our target is to decrease number of unindexed queries, you can track them in logs :
"RESULT err=0 tag=101 nentries=1 etime=0 notes=U"
And , of course improve performance .
So!

1. Change in acls:
(targetattr != "aci")(version 3.0; acl "VLV Request Control"; allow( read, search, compare, proxy ) userdn = "ldap:///anyone";)

2. ldapmodify -h host -p 389 -a -D "cn=Directory manager" -f file.ldif

dn: cn=no_netgroup_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass: top
objectClass: vlvSearch
cn: no_netgroup_vlv_index
vlvScope: 1
vlvBase: ou=netgroup,dc=test,dc=com
vlvFilter: (objectclass=nisNetGroup)
aci: (targetattr="*")(version 3.0; acl "VLV for Anonymous"; allow (read,search,compare) userdn="ldap:///anyone";)

dn: cn=no_group_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass: top
objectClass: vlvSearch
cn: no_group_vlv_index
vlvScope: 1
vlvBase: ou=group,dc=test,dc=com
vlvFilter: (objectClass=posixGroup)
aci: (targetattr="*")(version 3.0; acl "VLV for Anonymous"; allow (read,search,compare) userdn="ldap:///anyone";)

dn: cn=no_account_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass: top
objectClass: vlvSearch
cn: no_account_vlv_index
vlvScope: subtree
vlvBase: ou=people,dc=test,dc=com
vlvFilter: (objectClass=posixAccount)
aci: (targetattr="*")(version 3.0; acl "VLV for Anonymous"; allow (read,search,compare) userdn="ldap:///anyone";)

dn: cn=test.com.account,cn=no_account_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass:top
objectClass: vlvIndex
cn: test.com.account
vlvSort: cn uid

dn: cn=test.com.netgroup,cn=no_netgroup_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass:top
objectClass: vlvIndex
cn: test.com.netgroup
vlvSort: cn uid

dn: cn=test.com.group,cn=no_group_vlv_index,cn=no,cn=ldbm database,cn=plugins,cn=config
objectClass:top
objectClass: vlvIndex
cn: test.com.group
vlvSort: cn uid

Moving solaris zones between different hosts

2009-09-12T19:44:00.003+02:00

Suppose you have a Solaris zone (ZONE) on one host and want to move it on other global zone.
Then do following:
On first server:
1. zoneadm -z ZONE halt
2. zoneadm -z ZONE detach
3. cd $ZONEHOME
4. tar -cf ../zone.tar .
5. scp ../zone.tar user@server2:/$ZONEPATH

On the second server:

1. mkdir $ZONEHOME
2. cd $ZONEHOME
3. tar -xf ../zone.tar .
4. zonecfg -z ZONE
>create -a $ZONEHOME
>exit
5. zoneadm -z ZONE attach
6. zoneadm -z ZONE boot

Using Solaris JumpStart With the Solaris 10 OS for x86/x64 Platforms

2009-07-30T09:04:00.000+02:00

http://www.sun.com/bigadmin/features/articles/jumpstart_x86_x64.jsp

Ssh and nscd

2009-07-02T13:08:00.002+02:00

Strange behavior of sshd on Solaris 10:

If you use ldap as name service on Solaris 10 then you have use nscd daemon, ssh won't permit you log into without it.

How to examine content of certificates database

2009-06-30T10:02:00.004+02:00

/usr/sfw/bin/certutil -L -d /var/ldap/ - lists certificates in Solaris ldap client database

certutil -L -d /var/ldap/ -n certname -shows information about a certificate

Sun Directory Server backup scripts

2009-06-29T14:21:00.004+02:00

Sun Directory Server has quite good tools for backups. But if you want them to perform automaticaly you will have to create some cron scripts:

$cat backup.sh

#!/usr/bin/bash
DSADM=/opt/SUNWdsee/ds6/bin/dsadm
INSTANCE_NAME=instancename
INSTANCE_HOME=/var/spool/ldap_instances
INSTANCE_PATH=$INSTANCE_HOME/$INSTANCE_NAME
BACKUP_TIMESTAMP=`/usr/bin/date '+%H:%M:%S_%d:%m:%y'`
BACKUP_DIR=/var/backup/$INSTANCE_NAME/$BACKUP_TIMESTAMP
BACKUP_DIR_BINARY_DATA=/var/backup/$INSTANCE_NAME/$BACKUP_TIMESTAMP/binary

mkdir $BACKUP_DIR&&echo "*BACKUP DIRECTORY CREATED"
$DSADM stop $INSTANCE_PATH&&echo "*LDAP instance $INSTANCE_NAME - stopped"
$DSADM backup $INSTANCE_PATH $BACKUP_DIR_BINARY_DATA 2>&1 >/dev/null&&echo "*Binary data - backuped"
cp -r $INSTANCE_PATH/config $BACKUP_DIR&&echo "* Configuration data 1/2 copied"
cp -r $INSTANCE_PATH/alias $BACKUP_DIR/config&&echo "* Configuration data 2/2 copied"
$DSADM start $INSTANCE_PATH&&echo "*LDAP instance $INSTANCE_NAME - started"
echo "Saved data is under $BACKUP_DIR"

$cat restore.sh(don't put into crontab :)):

#!/usr/bin/bash

DSADM=/opt/SUNWdsee/ds6/bin/dsadm
SOURCE=$1
TARGET=$2

$DSADM stop $TARGET&& echo "Instance $TARGET stopped"
cp -r $SOURCE/config/alias/ $TARGET/config/&&echo "Config Data 1/2 restored"
cp -r $SOURCE/config/ $TARGET&& echo "Config Data 2/2 restored"
$DSADM restore $TARGET $SOURCE/binary/ && echo "Binary data restored"
$DSADM start $TARGET&& echo "Instance $TARGET started"

Solaris native LDAP client(Password policies)

2009-06-23T14:54:00.001+02:00

1. Password policies in Sun Directory Server are applied automaticaly (Default global password policy )
2. It's easy to create custom policies and apply them to different ldap trees(passwordpolicysubentry: cn=PolicyName,dc=test,dc=com)
3. In other words passwords policies works fine through LDAP, but user will see onle one reason of declining his password operation - "permission denied".

Solaris native LDAP client(using netgroups)

2009-06-23T14:49:00.003+02:00

If you want to define list of users and groups which are permited to use your exact host you need "netgroup" feature.

To use it in Solaris 10 it is necessary to:
1. Use "compat" in /etc/nsswitch.conf

#passwd: files ldap
#group: files ldap

passwd: compat
passwd_compat: ldap

group: compat
group_compat: ldap

2. Have installed proper pam modules (out of box on Solaris 10) and proper pam.conf

#
# Authentication management
#
# login service (explicit because of pam_dial_auth)
#
login auth requisite pam_authtok_get.so.1
login auth required pam_dhkeys.so.1
login auth required pam_unix_cred.so.1
login auth required pam_dial_auth.so.1
login auth binding pam_unix_auth.so.1 server_policy
login auth required pam_ldap.so.1
#
# rlogin service (explicit because of pam_rhost_auth)
#
# rlogin auth sufficient pam_rhosts_auth.so.1
rlogin auth requisite pam_authtok_get.so.1
rlogin auth required pam_dhkeys.so.1
rlogin auth required pam_unix_cred.so.1
rlogin auth binding pam_unix_auth.so.1 server_policy
rlogin auth required pam_ldap.so.1
#
# rsh service (explicit because of pam_rhost_auth,
# and pam_unix_auth for meaningful pam_setcred)
#
# rsh auth sufficient pam_rhosts_auth.so.1
rsh auth required pam_unix_cred.so.1
rsh auth binding pam_unix_auth.so.1 server_policy
rsh auth required pam_ldap.so.1
#
# PPP service (explicit because of pam_dial_auth)
#
ppp auth requisite pam_authtok_get.so.1
ppp auth required pam_dhkeys.so.1
ppp auth required pam_dial_auth.so.1
ppp auth binding pam_unix_auth.so.1 server_policy
ppp auth required pam_ldap.so.1
#
# Default definitions for Authentication management
# Used when service name is not explicitly mentioned for authentication
#
other auth requisite pam_authtok_get.so.1
other auth required pam_dhkeys.so.1
other auth required pam_unix_cred.so.1
other auth binding pam_unix_auth.so.1 server_policy
other auth required pam_ldap.so.1
#
# passwd command (explicit because of a different authentication module)
#
passwd auth binding pam_passwd_auth.so.1 server_policy
passwd auth required pam_ldap.so.1
#
# cron service (explicit because of non-usage of pam_roles.so.1)
#
cron account required pam_unix_account.so.1
#
# Default definition for Account management
# Used when service name is not explicitly mentioned for account management
#
other account requisite pam_roles.so.1
other account binding pam_unix_account.so.1
other account required pam_ldap.so.1
#
# Default definition for Session management
# Used when service name is not explicitly mentioned for session management
#
other session required pam_unix_session.so.1
#
# Default definition for Password management
# Used when service name is not explicitly mentioned for password management
#
other password required pam_dhkeys.so.1
other password requisite pam_authtok_get.so.1
other password requisite pam_authtok_check.so.1
other password required pam_authtok_store.so.1 server_policy
#
# Support for Kerberos V5 authentication and example configurations can
# be found in the pam_krb5(5) man page under the "EXAMPLES" section.
#

3. Proper content in LDAP
ldapaddent -a simple -D "cn=Directory Manager" -f /etc/netgroup netgroup

4. You have to attach groupname to the end of your passwd and shadow files:
Echo "+@groupname:x:::::" >>/etc/passwd
pwconv

5. Test if your netgroups and users works properly:
getent passwd
getent shadow

6. You will not be able to use "compat" if havn't defined groups, if don't need them use simple "ldap" declaration in nsswitch.conf!

Less known Solaris features

2009-06-17T14:41:00.000+02:00

A great book about less known Solaris features

Some tips using ssl with Sun Directory Server 6.3.1

2009-06-17T13:58:00.002+02:00

To make native ldap client using ssl with directory server perform following steps:

1. On directory server create/add own selfsigned/CAsigned certificates.
Don't use default ones(which are created during install), they are created with not FQDN.

2. Configure directory server(s) use them by default.

3. Export certificates in "der" format from each node you plan connect to(name them equal to domain names of servers):
/opt/SUNWdsee/ds6/bin/dsadm show-cert -F der -o CertName ldap_instance_name/logs/access "CertName"

4. Copy exported certificates to one place where you will import them into Solaris ldapclient's certificate database (in our case it's "cert_database").

5. Create certificate database:
/usr/sfw/bin/certutil -N -d ./cert_database

6. Import certificate(s):
/usr/sfw/bin/certutil -A -i ./CertName -n CertName -t CT -d ./cert_database

7. Distribute this database among all Solaris hosts which will use ldap, put it at /var/ldap directory.

8. Use ldapclient init ..... on each host.

9. Check everything works fine(on server):
tail -f ldap_instance_name/logs/access

That's all!

P.S: If you want secure communication in Directory Server replications, exchange certificates among each node also!

Webconsole on all interfaces

2009-06-16T13:38:00.002+02:00

Of cource, it's not a good idea to do it on production(for security reasons ;)),
but for testing purposes
#svccfg -s svc:/system/webconsole setprop options/tcp_listen = true

Export of rbac databases to ldap

2009-06-11T11:00:00.002+02:00

Beter use

#/usr/sadm/bin/smattrpop -c -f -v -s file:/servername -t ldap:/servername/dc=example,dc=com all

to export RBAC files to LDAP server.

Importing Projects database to LDAP

2009-06-05T10:13:00.002+02:00

`projects` Database

The default projects defined in /etc/project can be expressed in LDIF like this:

dn: solarisprojectname=system,ou=projects,dc=example,dc=com
objectClass: top
objectClass: solarisproject
SolarisProjectID: 0
SolarisProjectName: system

dn: solarisprojectname=user.root,ou=projects,dc=example,dc=com
objectClass: top
objectClass: solarisproject
SolarisProjectID: 1
SolarisProjectName: user.root

dn: solarisprojectname=noproject,ou=projects,dc=example,dc=com
objectClass: top
objectClass: solarisproject
SolarisProjectID: 2
SolarisProjectName: noproject

dn: solarisprojectname=default,ou=projects,dc=example,dc=com
objectClass: top
objectClass: solarisproject
SolarisProjectID: 3
SolarisProjectName: default

Files you have to import to LDAP for Solaris client proper work

2009-06-05T09:48:00.001+02:00

ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/aliases aliases
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/hosts ipnodes
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/rpc rpc
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/hosts hosts
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/protocols protocols
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/networks networks
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/services services
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/group group
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/netmasks netmasks
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/publickey publickey
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/aliases aliases
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/auto_home auto_home
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/auto_master auto_master
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/tsol/tnrhdb tnrhdb
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/tsol/tnrhtp tnrhtp
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/audit_user audit_user
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/auth_attr auth_attr
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/exec_attr exec_attr
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/security/prof_attr prof_attr
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/user_attr user_attr
ldapaddent -D "cn=Directory Manager" -w your_pass -f /etc/netmasks netmasks
ldapaddent -p -D "cn=Directory Manager" -w your_pass -f /etc/passwd passwd
ldapaddent -p -D "cn=Directory Manager" -w your_pass -f /etc/shadow shadow

Solaris LDAP client setup. part 2(management interface)

2009-06-04T13:49:00.002+02:00

Now we have an environment which uses LDAP as Name Service.
And the question of proper data management in LDAP arises.
We can use:

Sun Directory Server Webconsole Interface which is delivered with Directory server (which is a bad idea, you'll have to edit raw data) .
Use SMC (Solaris Management Interface) related tools. (Howto)

Problems which took a lot of time:
When run:

#/usr/sadm/bin/smrole list -D ldap:/solaris10core.example.test/dc=example,dc=test -- Use LDAP form of domain declaration(dc=,dc=), there are no word in manuals about it.
#/usr/sadm/bin/dtsetup scopes - be careful with domain name resolving for all domains this command shows.
Better run SMC in environment with END user cluster.

Solaris LDAP client setup. part 1

2009-05-28T16:49:00.004+02:00

Very simplified you can setup Solaris ldap user authentication in such steps.

On server side:
#/usr/lib/ldap/idsconfig
This tool inserts a lot of stuff in LDAP server(schemas, creates items tree, access creds, indexes search atributes etc.)

On client:
#ldapclient init -a profileName=prfilename server_ip_address
#ldapaddent -a simple -p -D "cn=Directory Manager" -f /etc/passwd passwd
#ldapaddent -a simple -p -D "cn=Directory Manager" -f /etc/group group
etc. more information in ldapaddent documentation
............

Everything goes fine, but passwords are not imported to ldap, to fix it you have manualy change password through Directory Server Control Console for each user. It actually can be coused by the fact my test environment used unencrypted communication between ldap server and client!

Postinstall configuration of Solaris zone

2009-05-28T08:31:00.001+02:00

When you have just installed a Solaris zone, you have to configure it to start working.
You can do it with zlogin -C command . The one of the first questions it asks is about terminal type you are using.
And here is some trick. Even if you do this from ssh session and $TERM variable is xterm you have to choose VT100 terminal.
In other case it hangs!

First steps to have Sun One Directory Server up and running

2009-05-27T16:43:00.002+02:00

To have DS up and running you have to go through several steps.
You are able to control directory server through command line tools(dsadm,dsconf) and by Java Web Console.
To use the second one you have :
1. Register Directory Service Control Center in Java Web Console
#/opt/SUNWdsee/dscc6/bin/dsccsetup ads-create
#/opt/SUNWdsee/dscc6/bin/dsccsetup status
#/opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads
#cacaoadm start
2.Start Java Web Console if necessary with the smcwebserver command
# /usr/sbin/smcwebserver start
3.Log into Directory Service Control Center with system user.
https://hostname:6789/
4. Create directory server instance.

Sun One Directory Server installation

2009-05-27T14:14:00.000+02:00

This directory server is included in product called Sun Java Enterprise System.
To install it on basic system it's necessary to install some extra packages.
For text based installation:
SUNWadmc,SUNWpl5u,SUNWadmfr,SUNWxcu4,SUNWadmfw,SUNWxcu6.
For GUI:
SUNWctpls,SUNWxwplr,SUNWmfrun,SUNWxwplt,SUNWxwfnt,SUNWxwrtl,SUNWxwice.

To begin installation unzip java_es-5-identsuite-ga-solaris-x86.zip and run
#./installer

During installation process you will be asked what components to install and proposed to configure them.
Installation log can be found in /var/sadm/install/logs/
and configuration report /var/sadm/install/logs/Java_Enterprise_System_Identity_Management_Suite_Summary_Report_install(Some number)

Installing zone support on basic Solaris 10 system

2009-05-26T10:11:00.000+02:00

This tip is about how to install zones(containers) support on Solaris 10
system(of course if you don't like to use full installations of Solaris)

To do it , install these packages regardless dependency warnings:
SUNWadmc
SUNWadmfr
SUNWadmfw
SUNWlur
SUNWlucfg
SUNWluu
SUNWpoolr
SUNWpool
SUNWluzone
SUNWzoner
SUNWzoneu

First steps to do after fresh installation of Solaris 10(core system) part 1

2009-05-25T11:16:00.001+02:00

1. Install bash,ssh,less(can't live without it):
mount /dev/dsk/c1t0d0p0 /mnt
#pkgadd -d /mnt/Solaris_10/Product/ SUNWbash
#pkgadd -d /mnt/Solaris_10/Product/ SUNWssh*
#pkgadd -d /mnt/Solaris_10/Product/ SUNWless

2. Generate key and enable ssh:
#ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
#svcadm enable ssh

3. Man pages will be useful also:
#pkgadd -d /cdrom/Solaris_10/Product SUNWdoc SUNWman

First steps to do after fresh installation of Solaris 10(core system) part 1

2009-05-25T11:11:00.000+02:00

From Debian with love!

2009-04-27T14:36:00.002+02:00

New Solaris packing system (IPS) and Debian's apt-get comparison.

Debian way of Solaris

2008-11-26T15:08:00.002+02:00

As you know a new packet management system (IPS) was released in a Open Solaris 2008.05.
The great event I thinks, It was the very necessary step towards greater usability of Solaris.
IPS is similar to Debian's APT or Aptitude and this is very good!
Great deal Ian Murdock !

I found a great article which will give you an overview of how it works.

Quick view at Solaris 10 10/08 Release

2008-11-05T16:58:00.006+02:00

As you know It was announced by SUN that it will be possible to install
Solaris 10/08 on ZFS filesystem directly.
I've checked how it works, you can watch it in the video report below.
I only can say that I've expected more: installer doesn't give ability to chose of what type of pool I want, I mean the process must be more customizable ... and hope that it will done in future releases.

Good article about Mysql Cluster deployed in Solaris Zones

2008-11-03T16:45:00.002+02:00

http://www.sun.com/bigadmin/features/articles/mysql_cluster_zones.jsp

Some usefull shell tricks

2008-06-04T17:35:00.006+02:00

Reuse previous arguments

The !$ command returns the last file name parameter used with a command. But what happens if you have a command that used multiple file names and you want to reuse just one of them? The !:1 operator returns the first file name used in a command. The example in Listing 1 shows how you can use this operator in combination with the !$ operator. In the first command, a file is renamed to a more meaningful name, but to preserve use of the original file name, a symbolic link is created. The file kxp12.c is renamed in a more readable manner, then the link command is used to create a symbolic link back to the original file name, in case it's still used elsewhere. The !$ operator returns the file_system_access.c file name, and the !:1 operator returns the kxp12.c file name, which is the first file name of the previous comma nd.

Listing 1. Using !$ and !:1 in combination

$ mv kxp12.c file_system_access.c
$ ln –s !$ !:1

Manage directory navigation with pushd and popd

UNIX supports a wide variety of directory-navigation tools. Two of my favorite productivity tools are pushd and popd. You're certainly aware that the cd command changes your current directory. What happens if you have several directories to navigate, but you want to be able to quickly return to a location? The pushd and popd commands create a virtual directory stack, with the pushd command changing your current directory and storing it on the stack, and the popd command removing the directory from the top of the stack and returning you to that location. You can use the dirs command to display the current directory stack without pushing or popping a new directory. Listing 2 shows how you can use the pushd and popd commands to quickly navigate the directory tree.

Listing 2. Using pushd and popd to navigate the directory tree

$ pushd . ~ ~
$ pushd /etc /etc ~ ~
$ pushd /var /var /etc ~ ~
$ pushd /usr/local/bin /usr/local/bin /var /etc ~ ~
$ dirs /usr/local/bin /var /etc ~ ~
$ popd /var /etc ~ ~
$ popd /etc ~ ~
$ popd ~ ~
$ popd

The pushd and popd commands also support parameters to manipulate the directory stack. Using the +n or -n parameter, where n is a number, you can rotate the stack left or right, as shown in Listing 3.

Listing 3. Rotating the directory stack

$ dirs /usr/local/bin /var /etc ~ ~
$ pushd +1 /var /etc ~ ~ /usr/local/bin
$ pushd -1 ~ /usr/local/bin /var /etc ~

Taken from here.

Using X server in Windows for calling remote graphical applications in Unix

2008-05-28T11:36:00.002+02:00

Sometimes you need ability to run X apps from remote unix servers.
It is not a problem when you are using unix as a client, but what should you do when you running windows.

The answer:
1. Your can use X servers for windows such as Xming is(I recommend this case if you are sure that this is the onliest task you will perform).
2. You can run X server from Cygwin

Lets examine the second one:
1. Install Cygwin and run it.
2. In shell run:
$XWin -logfile /tmp/asd.log -ac &
3. Connect to the desired host:
$ssh -X host
4. You have to export $DISPLAY variable with a value which points to host you have come from:
host$export DISPLAY=sourcehost:0.0
5. Run your apps:
host$xterm

Enabling shared folder in Citrix Metaframe client

2008-05-28T09:35:00.002+02:00

Often you need possibility send and receive files between remote and local machine through Citrix client.
I don't know why it is not enabled by default.
You have to add few lines to its config to [WFClient] section in "$HOME/.ICAClient/wfclient.ini" file:

DrivePathF=<ThePathToSharedFolder>
DriveEnabledF=On
DriveReadAccessF=On
DriveWriteAccessF=On

Check what package a file belongs to.

2008-05-27T16:36:00.002+02:00

There are two ways on Solaris:
1.pkgchk -p -l
2.grep filename /var/sadm/install/contents

Linux kernel interactive map

2008-05-14T10:50:00.007+02:00

I have found an interesting project which is very useful for understanding of linux kernel architecture:

Map is being updated ....

Solaris 10 networking configuration tips

2008-04-21T17:24:00.005+02:00

Files:
/etc/hostname.$interface - ip address /mask configuration of specific interface.
/etc/dhcp.$interface - if this file exists then dhcp agent will configure this $interface.
/etc/default/dhcpagent - dhcpagent configuration.
/etc/defaultrouter - containing hostnames or ip addresses of default routers.
/etc/nodename - hostname configuration
/etc/inet/ipnodes is a symlink on /etc/inet/hosts in Solaris 10.

Services:
svc:/network/physical:default - responsible for configuring network interfaces

Progs:
ndd - configures and provides information about tcp/ip settings (enable/disable ip forwarding .....)
ifconfig plumb $interface enables physical device.

Static routes:

# route -p add 192.168.15.0 192.168.15.1

The static routes will be stored in file /etc/inet/static_routes.

Interface multipathing(non probe based):

hostname.qfe0
hostname group groupname up

hostname.qfe4
group groupname up

for non-persistant configuration:

ifconfig qfe0 plumb; ifconfig qfe0 ip mask group groupname up

ifconfig qfe4 plumb;ifconfig qfe4 group groupname up

sys-unconfig

2008-04-17T16:49:00.002+02:00

Sys-unconfig- the very helpful tool when you want to begin configuration of system from scratch.

Do not confuse with configuration files of NFS in Solaris.

2008-03-29T16:23:00.003+02:00

Some unix admins misunderstand NFS configs, while working with this system. So lets examine most used files.

/etc/dfs/sharetab:
As list, maintained by the kernel , that contains resources currently being shared by NFS server

/etc/rmtab:
A list, maintained by the kernel, that contains local file systems that are remotely mounted by NFS clients.

/etc/vfstab:
A configuration list of resources to mount when mountall is executed.

/etc/mnttab:
A list, maintained by the kernel, that contains all file systems that are mounted.

/etc/dfs/dfstab:
A configuration list of resources to share when the NFS server is started or when shareall is executed.

Solaris Soft Partitioning

2008-03-25T10:36:00.005+02:00

This is a very good guide for Solaris Soft Partitioning, I took it from http://sysunconfig.net/unixtips/soft-partitions.html

The intent of this document is to describe Soft Partitioning within Solstice DiskSuite (soon-to-be-renamed Solaris Volume Manager), and offer a short primer/tutorial on how to create, use, and delete them.

Until now, Solaris, without any volume management software, has only ever allowed a fixed number of partitions on a physical disk (seven (7) on SPARC platforms). With the increase in capacity of disks, this limitation has become a severe restriction.

SDS/SVM uses these slices for its metadevices (sub-mirrors, trans, stripes, and RAID5) and hence is faced with the same limitation, whereas Veritas Volume Manager (VxVM) allows for the logical partitioning of disks into a virtually unlimited number of subdisks.

Soft Partitioning allows for a disk to be subdivided into many partitions which are controlled and maintained by software, thereby removing the limitation of the number of partitions on a disk. A soft partition is made up of one or more "extents". An extent describes the parts of the physical disk that make up the soft partition. While the maximum number of extents per soft partition is 2147483647, the majority of soft partitions will use only one (1) extent.

What is new?

Soft Partitioning was not in the original Solstice DiskSuite 4.2.1 Release, which coincided with the release of Solaris 8. However, the soft partitioning functionality was released in patch 108693-06 for SDS 4.2.1.

When Solaris 9 gets released, the "Solstice DiskSuite" name will change to "Solaris Volume Manager" ("SVM") and it will be bundled in with Solaris 9. Soft Partitioning will, of course, be part of the base functionality of that release.

Soft Partitions are implemented by new kernel driver: md_sp.

   # modinfo | grep md_sp
228 78328000 4743 - 1 md_sp (Meta disk soft partition module)

There are new options to the metainit command:

   metainit softpart -p [-e] component size
metainit softpart -p component -o offset -b size

The metattach command has been modified to allow for growing of soft partitions:

   metattach softpart size

There is a new command... metarecover:

   metarecover [-n] [-v] component -p [-d|-m]

NOTE: the -p option means that the command refers to soft partitions.

Creating Soft Partitions

There are three methods to create a soft partition using the metainit command:

Specifying an unused disk and size (with the -e option). For example:

   # metainit d0 -p -e c1t0d0 200m

The -e option requires that the name of the disk supplied be in the form c#t#d#.

The last parameter (200m) specifies the initial size of the soft partition. The sizes can be specified in blocks, kilobytes, megabytes, gigabytes, and terabytes.

The -e option causes the disk to be repartitioned such that slice 7 has enough space to hold a replica (although no replica is actually created on this disk) and slice 0 contains the rest of the space. Slice 2 is removed from the disk. The soft partition that is being created is put into slice 0. Further soft partitions can be created on slice 0 by the next method of creating a soft partition.

After this command is run, the layout of the disk would like similar to this example:

   Part      Tag   Flag   Cylinders     Size           Blocks
0 unassigned   wm     5 - 2035   999.63MB   (2031/0/0) 2047248
1 unassigned   wm     0            0        (0/0/0)          0
2 unassigned   wm     0            0        (0/0/0)          0
3 unassigned   wm     0            0        (0/0/0)          0
4 unassigned   wm     0            0        (0/0/0)          0
5 unassigned   wm     0            0        (0/0/0)          0
6 unassigned   wm     0            0        (0/0/0)          0
7 unassigned   wu     0 -   4      2.46MB   (5/0/0)       5040

This command (with the -e) can only be run on an empty disk (one that is not used in any other metadevice). If another metadevice or replica already exists on this disk, one of the following messages will be printed, and no soft partition will be created.

   metainit: hostname: c#t#d#s0: has appeared more than once in the specification of d#

   metainit: hostname: c#t#d#s#: has a metadevice database replica

Specifying an existing slice name and size (without the -e option). This will be the most common method of creation. For example:
# metainit d1 -p c1t0d0s0 1g
This will create a soft partition on the specified slice. No repartitioning of the disk is done. Provided there is space on the slice, additional soft partitions could be created as required. The device name must include the slice number (c#t#d#s#).
If another soft partition already exists in this slice, this one will be created immediately after the existing one. Therefore, no overlap of soft partitions can occur by accident.
Specifying an existing slice and absolute offset and size values. For example:
# metainit d2 -p c1t0d0s0 -o 2048 -b 1024
The -o parameter signifies the offset into the slice, and the -b parameter is the size for the soft partition. All numbers are in blocks (a block is 512 bytes). The metainit command ensures that extents and soft partitions do not overlap. For example, the following is an attempt to create overlapping soft partitions.
# metainit d1 -p c1t0d0s0 -o 1 -b 2024
d1: Soft Partition is setup
# metainit d2 -p c1t0d0s0 -o 2000 -b 2024
metainit: hostname: d2: overlapping extents specified
An offset of 0 is not valid, as the first block on a slice containing a soft partition contains the initial extent header. Each extent header consumes 1 block of disk and each soft partition will have an extent header placed at the end of each extent. Extent headers are explained in more detail in the next section.
NOTE: This method is not documented in the man page for metainit and is not recommended for manual use. It is here because a subsequent metastat -p command will output information in this format.

Extent Headers

Whenever a soft partiton is created in a disk slice, an "extent header" is written to disk. Internally to Sun, these are sometimes referred to as "watermarks".

An extent header is a consistency record and contains such information as the metadevice (soft partition) name, it's status, it's size, and a checksum. Each extent header 1 block (512 bytes) in size.

The following diagram shows an example 100MB slice (c1t0d0s0) and the extent headers (watermarks) that have been created on it. The command to make the soft partition shown was

   # metainit d1 -p c1t0d0s0 20m

->>

There is always an extent header on the first and last blocks in the slice. Note that the 80MB of space left over from the creation of the soft partition can be used to make one or more additional soft partitions. Each additional soft partition will create an additional extent header to be created as well.

Mirroring Soft Partitions

Once you have created soft partitions, what can you do with them? Well, one thing to do is to create mirrors out of them. Unfortunately, even though a soft partition is a metadevice, they cannot serve directly as a submirror. For example:

   # metainit d10 -p c1t11d0s4 100m
d10: Soft Partition is setup
# metainit d20 -m d10
metainit: hostname: d10: invalid unit

Instead, you must first take the soft partition and create a simple concat/stripe out of it. For example:

   # metainit d10 -p c1t0d0s0 100m
d10: Soft Partition is setup
# metainit d20 1 1 d10
d20: Concat/Stripe is setup
# metainit d30 -m d20
d30: Mirror is setup

# metainit d11 -p c2t0d0s0 100m
d11: Soft Partition is setup
# metainit d21 1 1 d11
d21: Concat/Stripe is setup
# metattach d30 d21
d30: submirror d21 is attached

Once done, the resulting metastat output of the mirror will look like this:

   # metastat d30

d30: Mirror
 Submirror 0: d20
   State: Okay
 Submirror 1: d21
   State: Okay
 Pass: 1
 Read option: roundrobin (default)
 Write option: parallel (default)
 Size: 204624 blocks

d20: Submirror of d30
 State: Okay
 Size: 204624 blocks
 Stripe 0:
     Device              Start Block  Dbase State        Hot Spare
     d10                        0     No    Okay

d10: Soft Partition
 Component: c1t0d0s0
 State: Okay
 Size: 204800 blocks
     Extent              Start Block              Block count
          0                        1                   204800

d21: Submirror of d30
 State: Okay
 Size: 204624 blocks
 Stripe 0:
     Device              Start Block  Dbase State        Hot Spare
     d11                        0     No    Okay

d11: Soft Partition
 Component: c2t0d0s0
 State: Okay
 Size: 204800 blocks
     Extent              Start Block              Block count
          0                        1                   204800

Combining Soft Partitions Together into a RAID5 Device

RAID5 devices can be made up of soft partitions directly. This example shows 4 soft partitions (from 4 separate slices) striped together to make a RAID5 device:

   # metainit d1 -p c1t0d0s0 10m
d1: Soft Partition is setup
# metainit d2 -p c2t0d0s0 10m
d2: Soft Partition is setup
# metainit d3 -p c3t0d0s0 10m
d3: Soft Partition is setup
# metainit d4 -p c4t0d0s0 10m
d4: Soft Partition is setup
# metainit d10 -r d1 d2 d3 d4
d10: RAID is setup

Once done, the resulting metastat output of the RAID5 device will look like this:

   # metastat d10

d10: RAID
 State: Okay
 Interlace: 32 blocks
 Size: 59472 blocks
Original device:
 Size: 60384 blocks
     Device              Start Block  Dbase State        Hot Spare
     d1                       330     No    Okay
     d2                       330     No    Okay
     d3                       330     No    Okay
     d4                       330     No    Okay

d1: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                        1                    20480

d2: Soft Partition
 Component: c1t0d4s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                        1                    20480

d3: Soft Partition
 Component: c1t1d1s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                        1                    20480

d4: Soft Partition
 Component: c1t1d3s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                        1                    20480

Using Soft Partitions for MetaTrans (UFS Logging) Devices

MetaTrans devices (UFS logging) can be built on top of soft partitions. Soft partitions can be used for the master device, the logging device, or both. In the following example, soft partitions are used for both the master and the logging device:

   # metainit d1 -p c1t0d0s0 500m
d1: Soft Partition is setup
# metainit d2 -p c2t0d0s0 50m
d2: Soft Partition is setup
# metainit d10 -t d1 d2
d1: Trans is setup

Once done, the resulting metastat output of the metatrans device will look like this:

   # metastat d10
d10: Trans
 State: Okay
 Size: 1024000 blocks
 Master Device: d1
 Logging Device: d2

d1: Soft Partition
 Component: c1t1d3s0
 State: Okay
 Size: 1024000 blocks
     Extent              Start Block              Block count
          0                        1                  1024000

d2: Logging device for d10
 State: Okay
 Size: 102142 blocks

d2: Soft Partition
 Component: c1t1d1s0
 State: Okay
 Size: 102400 blocks
     Extent              Start Block              Block count
          0                        1                   102400

Layering

Most of the time, soft partitions are made on a disk slice. However, there are certain situations where it can be beneficial to make a soft partition on top of an existing metadevice. This is referred to as layering.

For example, say you have a 90GB RAID5 device made up of 6 18GB disks. You can then take that 90GB device and "split it up" into many soft partitions. These many soft partitions then can be accessed as separate simple metadevices, although the data in them is protected by the RAID5 parity in the underlying device.

Soft partitions can be layered only on top of concat/stripes, mirrors, and RAID5 devices. Soft partitions cannot be layered on top of a metatrans device or directly on top of another soft partition.

Here is an example of layering soft partitions on top of an existing RAID5 metadevice. First, we create the RAID5 device, then soft partition that device into 3 100MB partitions (obviously, we could create more than just 3 soft partitions).

   # metainit d0 -r c1t0d2s0 c1t0d4s0 c1t1d1s0 c1t1d3s0
d0: RAID is setup

# metainit d1 -p d0 100m
d1: Soft Partition is setup
# metainit d2 -p d0 100m
d2: Soft Partition is setup
# metainit d3 -p d0 100m
d3: Soft Partition is setup

Each of the resulting soft partitions (d1, d2, and d3) can be accessed individually (i.e., newfs and mount).

Soft partitions can be built on top of an existing mirror device as well, just like we did above on the RAID5 device. In the following example, the mirror device (d0) is "carved up" into 3 smaller soft partitions.

   # metainit d10 1 1 c1t0d2s0
d10: Concat/Stripe is setup
# metainit d20 1 1 c2t0d0s0
d20: Concat/Stripe is setup
# metainit d0 -m d10 d20
d0: Mirror is setup

# metainit d1 -p d0 100m
d1: Soft Partition is setup
# metainit d2 -p d0 100m
d2: Soft Partition is setup
# metainit d3 -p d0 100m
d3: Soft Partition is setup

Soft partitions are not allowed to be parented by other soft partitions directly. For example:

   # metainit d1 -p c1t0d0s0 100m
d1: Soft Partition is setup
# metainit d2 -p d1 10m
metainit: hostname: d1: invalid unit

Soft partitions also cannot be built on top of trans (UFS logging) devices. For example:

   # metainit d1 -t d10 d20
d1: Trans is setup
# metainit d2 -p d1 100m
metainit: hostname: d1: invalid unit

Growing Soft Partitions

A soft partition can be grown by the use of the metattach command. There is no mechanism to shrink a soft partition.

   # metattach d0 10m
d0: Soft Partition has been grown

When additional space is added to an existing soft partition, the additional space is taken from any available space on the same device and might not be contiguous with the existing soft partition. Growing soft partitions must be done with free space in the same device as the current soft partition.

The following example shows how growing a soft partition will increase the size of the current extent:

   # metainit d1 -p c1t0d2s0 100m
d1: Soft Partition is setup
# metastat d1
d1: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 204800 blocks
     Extent              Start Block              Block count
          0                        1                   204800

# metattach d1 50m
d1: Soft Partition has been grown
# metastat d1
d1: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 307200 blocks
     Extent              Start Block              Block count
          0                        1                   307200

Note how after the metattach is run, there is still only one extent, but the (block count) has grown from 204800 (100MB) to 307200 (150MB).

In the following example, the extent cannot be grown, as it was above, because another soft partition is "in the way". Therefore, a second extent is created in the same slice.

   # metainit d1 -p c1t0d2s0 100m
d1: Soft Partition is setup
# metainit d2 -p c1t0d2s0 10m
d2: Soft Partition is setup
# metastat
d1: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 204800 blocks
     Extent              Start Block              Block count
          0                        1                   204800

d2: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                   204802                    20480

# metattach d1 50m
d1: Soft Partition has been grown
# metastat
d1: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 307200 blocks
     Extent              Start Block              Block count
          0                        1                   204800
          1                   225283                   102400

d2: Soft Partition
 Component: c1t0d2s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                   204802                    20480

Note how d1 now has two non-contiguous extents that together make up the 307200 (150MB) blocks.

NOTE: Growing the metadevice does not modify the data or the filesystem inside the metadevice. If the metadevice contains a filesystem, you must use the appropriate command(s) to grow that filesystem after the metadevice has been grown.

Deleting Soft Partitions

This is achieved by using the metaclear command in the normal way:

   # metaclear d0
d0: Soft Partition is cleared

If other metadevices are using the soft partition, the metaclear will error with:

   metaclear: hostname: d0: metadevice in use

Using Soft Partitions with Disksets

There are no differences with soft partitioning in a diskset, other than having to specify the -s option on the commandline to specify the diskset name.

The only potential problem occurs when dealing with did disk devices that are in a SunCluster configuration. Unfortunately, the naming convention of the did devices is similar to that of SDS/SVM in that the disks are referred to as d#. This means that SDS/SVM could confuse a did disk with a metadevice when creating a soft partition.

The simple workaround to this problem is to use the full path to the did device on the metainint commandline in order to prevent any confusion.

For example, the following command to create a 1GB soft partition on /dev/did/rdsk/d7s0 would be invalid:

   # metainit -s set2 d0 -p d7s0 1g

Instead, the correct command to run would be:

   # metainit -s set2 d0 -p /dev/did/rdsk/d7s0 1g

How to list the soft partitions in a given slice

The metarecover command, with the -n and -v options, will display information about the soft partitons existing in a given slice.

The metarecover command actually scans the given slice for extent headers and prints the information that it finds about those headers.

In each slice/device, there are also 2 additional extent headers; one which preceeds the free space in the slice, and the one on the last block of the slice. These are printed as well. This is an easy way to determine how much free space is available in a slice for additional soft partitions.

   # metarecover -v -n /dev/rdsk/c1t0d0s0 -p
Verifying on-disk structures on c1t0d0s0.
The following extent headers were found on c1t0d0s0.
Name  Seq#    Type          Offset          Length
d0     0   ALLOC               0           20481
d1     0   ALLOC           20481           40961
NONE     0     END        17674901               1
NONE     0    FREE           61442        17613459
Found 2 soft partition(s) on c1t0d0s0.

In the above example, there were 2 soft partitions (d0 and d1) found on c1t0d0s0, as well as 17613458 blocks (approx 8.4GB) of unallocated free space.

IMPORTANT NOTE: The information printed by this command is relative to the extent header, not the soft partition itself. Therefore, the 'offset' is the starting location of the extent header, not the extent itself. Also, the 'length' given is the length of the extent plus the header. Therefore, in the example above, there are only 17613458 free blocks, not 17613459 blocks.

Because soft partitions can be layered above metadevices like mirrors or RAID5 devices (see layering, above), this command can also be run on them to determine the locations and sizes of the extent headers. In the example below, d0 is a RAID5 metadevice which has 4 soft partitions in it. There is no free space left in this device.

   # metarecover -v -n d0 -p
Verifying on-disk structures on d0.
The following extent headers were found on d0.
             Name  Seq#    Type               Offset               Length
               d1     0   ALLOC                    0               204801
               d2     0   ALLOC               204801               204801
               d3     0   ALLOC               409602               204801
              d99     0   ALLOC               614403              7573580
             NONE     0     END              8187983                    1
Found 4 soft partition(s) on d0.

Fragmentation

Fragmentation of free space will occur on a slice when there has been activity in creating, deleting, and possibly growing soft partitions. At this time, there is no method to defragment a disk.

For example, the following sequence of commands can result in some amount of fragmentation. First, create 2 10MB soft partitions on a slice.

   # metainit d1 -p c1t0d0s0 10m
d1: Soft Partition is setup
# metainit d2 -p c1t0d0s0 10m
d2: Soft Partition is setup

Then, remove the first 10MB soft partition and then create a 20MB soft partition.

   # metaclear d1
d1: Soft Partition is cleared
# metainit d3 -p c1t0d0s0 20m
d3: Soft Partition is setup

When the d3 metadevice was created, the 10MB of free space at the beginning of the slice is not used, because there is a contiguous 20MB space available further out that can be used instead. Therefore, the 10MB of free space is skipped over in favor of the first 20MB of contiguous space. The metarecover command will show the fragmentation (multiple free spaces):

   # metarecover -v -n c1t0d0s0 -p
Verifying on-disk structures on c1t0d0s0.
The following extent headers were found on c1t0d0s0.
          Name  Seq#    Type               Offset               Length
            d2     0   ALLOC                20481                20481
            d3     0   ALLOC                40962                40961
          NONE     0     END              2047247                    1
          NONE     0    FREE                81923              1965324
          NONE     0    FREE                    0                20481
Found 2 soft partition(s) on c1t0d0s0.

Recovering Soft Partitions

The 'metarecover' command is run when something has gone wrong. It should not be run except to recover from a catastrophic problem. There are two main functions that this command does. It can

scan through the given slice and recreate the soft partitions that it finds there. this is good when moving a disk with soft partitions to a new machine. The option to use on the metarecover command is -d.
reads through the current replica and creates the soft partitions on the given slice. This is good to run after a disk fails and gets replaced with a new one. The option to use on the metarecover command is -m.

Recreating Information in the Replica from the Extent Headers

Here is a very simple example showing a disk which had soft partitions created on it (in slice 0) on another host, which is being moved to a new machine. We wish to extract the soft partitions on this new machine. Currently, there are no metadevices created.

   # metastat

This command scans the given slice (in this case, "c0t0d0s0") and, for each soft partition it finds in that slice, it puts an entry into the current replica. The data on the disk is not modified, and nothing on the slice specified is modified. All that happens is that the extent headers are read and information is written to the replica.

   # metarecover c0t0d0s0 -p -d
The following soft partitions were found and will be added to
your metadevice configuration.
Name            Size     No. of Extents
d1           61440         1
d2           20480         1
WARNING: You are about to add one or more soft partition
metadevices to your metadevice configuration.  If there
appears to be an error in the soft partition(s) displayed
above, do NOT proceed with this recovery operation.

Are you sure you want to do this (yes/no)? yes

c0t0d0s0: Soft Partitions recovered from device.

Now, we can see the soft partition metadevices have been created for us:

   # metastat
d1: Soft Partition
 Component: c0t0d0s0
 State: Okay
 Size: 61440 blocks
     Extent              Start Block              Block count
          0                   120836                    61440

d2: Soft Partition
 Component: c0t0d0s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                    20482                    20480

Recreating Soft Partitions from Information in the Replica

This example essentially does the opposite of example 1. In this case, the actual extent headers on the disk have been lost, either because something wrote over them, or because the disk hosting the soft partitions had to be replaced with new disk drive. Although the replica shows the soft partitions to be "Okay":

   # metastat
d1: Soft Partition
 Component: c0t0d0s0
 State: Okay
 Size: 61440 blocks
     Extent              Start Block              Block count
          0                   120836                    61440

d2: Soft Partition
 Component: c0t0d0s0
 State: Okay
 Size: 20480 blocks
     Extent              Start Block              Block count
          0                    20482                    20480

there are no extent headers on the disk, so I/O to the disk will error out.

   # dd if=/dev/zero of=/dev/md/rdsk/d2
dd: /dev/md/rdsk/d2: open: I/O error

To check the disk to see if any extent headers exist on the disk, you can run the command

   # metarecover -n c0t0d0s0 -p
found incorrect magic number 0, expected 20000127.
No extent headers found on c0t0d0s0.
c0t0d0s0: On-disk structures invalid or no soft partitions found.
metarecover: hostname: d0: bad magic number in extent header

The above command confirms that there are no extent headers on the disk. To have the extent headers written out to the disk, according to the information currently in the replica, run the command

   # metarecover c0t0d0s0 -p -m
c0t0d0s0: Soft Partition metadb configuration is valid

WARNING: You are about to overwrite portions of c0t0d0s0
with soft partition metadata. The extent headers will be
written to match the existing metadb configuration.  If
the device was not previously setup with this
configuration, data loss may result.

Are you sure you want to do this (yes/no)? yes

c0t0d0s0: Soft Partitions recovered from metadb

Now, the extent headers have been written to the disk, so I/O will work correctly now. Running the verify command again, we see

   # metarecover -n c0t0d0s0 -p
c0t0d0s0: Soft Partition metadb configuration is valid
c0t0d0s0: Soft Partition metadb matches extent header configuration

Splitting two monitors in xorg

2008-03-18T17:41:00.001+02:00

It was done in Ubuntu Linux 7.10 but must work on most Unixes where RandR is ported.

About RandR:

The RandR 1.2 extension first appeared in Xserver 1.3 (i.e DebianTesting, since 2007-08-21). It provides automatic discovery of modes (resolutions, refresh rates, ...) together with the ability to configure outputs dynamically (resize, rotate, move, ...).

As of today, the following drivers/boards support RandR 1.2:

the Intel driver on all boards (since 1.9.91),
the NV driver on G80 boards (since 2.0.95),
the ATI driver on r200/r300/r400/r500/r600 boards (since 6.7.191) where RandR 1.2 replaces MergedFB,
the MGA driver on all boards (since 1.9.99)
the RadeonHD driver on r500/r600 boards (since 1.1)

Other drivers still use the old/hard/non-standard way to configure modes.

There are 3 ways of doing this:
1. From graphical tool in your desktop environment. In Ubuntu this function was disabled for my video driver "intel". Very strange , because it supports these (may be because of experimental status ... :).
2. From command line : xrandr tool, good way of doing it but I am man who likes things to be done automatically :).
3. Xorg files customization - not very easy for newbies but most flexible and you actually have to do it once.

Hardware:

1. Laptop Dell D630
$lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
03:01.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 21)
03:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

2. External monitor Samsung 710n

How to do it with xrundr.

Monitor is on the left of my laptop.
So to do it from command line;
1. $xrandr --output LVDS --right-of VGA --auto
Output will say that we must insert size of virtual work space to xorg.conf .
Display section of Screen must looks like this:
SubSection "Display"
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
Virtual 2720 1024
EndSubSection
Actually we need this virtual string.
2. Restart X server.
3. Repeat "$xrandr --output LVDS --right-of VGA --auto"
4. We have two splited monitors.

But I did it in xorg.conf.

Problems:
Strange behavior of xorg:usage of RightOf for the 1 monitor is not the same as using LeftOf with 2 monitor object of xorg.conf.
It works correctly when use these option with the default monitor.

My xorg.conf:

Section "Files"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
Option "monitor-LVDS" "Dell Monitor"
Option "monitor-VGA" "SyncMaster"
EndSection

Section "Monitor"
Identifier "Dell Monitor"
Option "DPMS"
HorizSync 30-70
VertRefresh 50-160
Option "PreferredMode" "1440x900"
# Option “Position” “0 0″
Option "RightOf" "SyncMaster"
EndSection

Section "Monitor"
Identifier "SyncMaster"
Option "DPMS"
HorizSync 30-81
VertRefresh 56-75
# Option “Position” “1440 0″
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller"
Monitor "Dell Monitor"
DefaultDepth 24
SubSection "Display"
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
Virtual 2720 1024
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

Reference : http://intellinuxgraphics.org/dualhead.html

Solaris Zones

2008-03-03T17:02:00.000+02:00

From the point of view of Linux administrator Solaris zones can be compared with Linux's both vserver and xen.
Exist two kinds of zones: global and non-global.

global - have access to all hardware resources, this zone is used for system wide administration.
non-global - shares operation under the Solaris kernel booted from the global zone, not aware of physical device paths, and not aware of the existence of other zones, no zone (including itself) can be managed from this zone.

Create a zone named test-zone (as an example) by issuing the following command:
# zonecfg -z test-zone
If you are configuring this zone for the first time, the following system message will appear:
test-zone: No such zone configured
Use 'create' to begin configuring a new zone.
Create the configuration for the test-zone by issuing the create command at the zone prompt:
#zonecfg:test-zone> create
Set the zone path to, for example, /export/home/test-zone:
#zonecfg:test-zone> set zonepath=/export/home/test-zone
Set the value of the autoboot property so that the zone is automatically booted when the global zone is booted.
#zonecfg:test-zone> set autoboot=true
Add the virtual network interface to the zone test-zone.Start setting up the interface with the following command:
#zonecfg:test-zone> add net

Assign the IP address 192.168.1.11 to the network interface.
#zonecfg:test-zone:net> set address=192.168.1.11
Set the physical device type for the network interface, such as pcn0.
#zonecfg:test-zone:net> set physical=pcn0
End this specification for the resource net:
#zonecfg:test-zone:net> end
The prompt returns back to the zone level:
#zonecfg:test-zone>
Exit the zonecfg command:
#zonecfg:test-zone> exit

At this stage we our zone configured.
Now we can install it:
#zoneadm -z test-zone install
To make zone up and running:
#zoneadm -z test-zone boot

To login to zone:
#zlogin test-zone

Getting ip address of device when you even don't know MAC.

2008-02-28T12:32:00.004+02:00

It is quite common situation when you need to know ip address of some network device
(for example, you have forgotten ip address of IPMA interface of a running server or active switch ...).
Actually you can even don't know mac address(know nothing about connected device except that it is up and running).
You can do it with arping utility, which you can find in most unix/linux distributions.

So lets examine 2 cases:
1. You want to know ip and mac address of directly attached device(you don't have access to it's console...),then:
#arping -i interface_name ff:ff:ff:ff:ff:ff
You will see something like this.
60 bytes from 10.10.101.14 (00:22:ba:c7:c8:c0): icmp_seq=0 time=26.941 usec

2. You know mac address and want to know ip:
#arping -i interface_name "target mac address"

There are two different arping utilities. One is a part of iproute2 utils and is "Linux only". The second one is from
Thomas Habets <thomas@habets.pp.se>
It can be downloaded from ftp://ftp.habets.pp.se/pub/synscan/.
I have used the second one.

PS:These method don't give 100% guaranty, because some devices block ICMP broadcasts.

Role Based Access Control by Solaris 10

2008-02-25T12:55:00.002+02:00

Let's examine Solaris RBAC terminology.

1. Roles - is the highest level of abstraction in Solaris RBAC, it is special type of account which
inherits security attributes from profiles.
Place of definition: /etc/user_attr file.

2. Profiles - combine authorities and commands(with different uid,euid,gid,egid and privileges).
Defined in two files: /etc/security/exec_attr and /etc/security/prof_attr

3. Authorizations - defines class of actions that you can perform.
Example: Solaris.device.cdrw - permits users read-write operations on CD-ROM.
Authorizations are defined in /etc/security/auth_attr file.

But I don't suggest to edit these files directly, use special tools as much as possible.

So lets try to create custom profile-> create role -> assign it to a user.

1. Log on to the machine as root or assume the primary administrator role.
2. Edit the /etc/security/prof_attr file and add the following line to it:
PrintOpr:::Can perform printer related tasks:profiles=Printer Management, All
Save the file and exit.
3. Create a role with name printRole and assign it the PrintOpr profile (remember, the profile name is case sensitive) by issuing the following command:
roleadd -P PrintOpr printRole
4.Set the password for this role by using the passwd command:
passwd printRole
5. Create a user with name testuser and assign it the role printRole:
useradd -R printRole -d <dirName> testuser
where <dirName> specifies the full path to the home directory that will be assigned to the user being created.
6. Set the password for testuser by issuing the passwd command:
passwd testuser
7. Test that the role has been created and assigned to the user:Log out, and log in as testuser.Issue the roles command to see whether the testuser has the role assigned to it:
roles
Assume the role:
su printRole
Display the profiles that are assigned to this role:
profiles

Solaris 10 have several predefined profiles also:
Primary administrator. This rights profile consists of all the rights of a superuser.
System administrator. This profile contains most of the rights except for security-related rights. It provides the ability to perform
most non-security administrative tasks, such as printer management, cron management, device management,
file system management, mail management, backup and restore, name service management,
network management, software installation, and process and user management. However, it includes several other profiles, which makes it a powerful profile.
Operator. This profile contains limited rights to manage files and offline media. It provides the ability to perform backups and printer maintenance.
By default, it does not include the rights to restore files.
Printer management. This profile consists of a limited number of authorizations and commands to handle printing.
Basic Solaris user. This profile enables users to use the Solaris system within the security boundaries set up on the system.
This profile is assigned, by default, to all the Solaris users.
All. This profile consists of commands that do not have security attributes.

Solaris Software RAID (mirroring)

2008-02-19T17:58:00.004+02:00

Solaris Volume Manager gives an ability create software raid, currently it supports 0,1,5,0+1,1+0 levels.
Lets make a mirror of root partition which we already are using.

1. Backup /etc/vfstab and /etc/system before you go ahead.

2. It is necessary to prepare space for state database , on running box we can redistribute swap area.
#swap -d /dev/dsk/yourswappart
Before redistributing space we must comment string for swap partition out in vfstab,
because format utility will consider this partition is being used.
Decrease size of current swap partition on 30mb and use this free space for state database partiotion.
Do it with format utility:
#format
Enable swap again
#swap -a /dev/dsk/yourswappart

3. Mirrored partitions must equal in size or we will waste space.
This commands will copy partition table to second drive
# prtvtoc /dev/rdsk/c0d0s0 | fmthard -s - /dev/rdsk/c0d1s0

3.1Specify the master boot program.
# fdisk -b /usr/lib/fs/ufs/mboot /dev/rdsk/c0d1s0

3.2
Make the secondary disk bootable.
# /sbin/installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1d1s0

3.3
Make the secondary disk bootable. (SPARC)
installboot /usr/platform/sun4u/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0

4. Create state database on small slices created recently.
# metadb -f -a -c3 c0d0s3
# metadb -a -c3 c0d1s3

5. Create submirrors :
#metainit -f d10 1 1 c0d0s0
#metainit -f d20 1 1 c0d1s0

6. Create mirror device and add one submirror first:
#metainit d0 -m d10
# lockfs -fa (clear improper file locks)

7. Add to /etc/system file:
set md:mirrored_root_flag=1

8. Create submirrors for swap:
#metainit -f d30 1 1 c0d0s3
#metainit -f d40 1 1 c0d1s3

9. Create mirror d1 and include submirors:
#metainit d1 -m d30
Edit /etc/vfstab to contain correct information about swap.

10. Reboot.

11. Add other submirrors into mirrors:
#metatach d0 d20
#metatach d1 d40

11.1. Add to GRUB additional disk:

title alternate boot
root (hd1,0,a)
kernel /boot/multiboot
module /boot/x86.miniroot-safe

12. Verify that process of synchronization have begun:
#metastat

Backward process(unmirroring).

To unmirror you have to do something like these:
#metadetach d0 d20
#metaroot /dev/dsk/c0d0s0
#metadetach d1 d40
Correct /etc/vfstab.
Reboot.
Do not run the last command if you have other raids running - it will destroy them!!
#metaclear -a

SPARC NOTES:

# ls -l /dev/dsk/c0t1d0s0
lrwxrwxrwx 1 root root 88 Feb 8 15:51 /dev/rdsk/c1t3d0s0 ->
../../devices/pci@1f,0/pci@1,1/ide@3/dad@0,0:a
# init 0
ok nvalias backup_root /pci@1f,0/pci@1,1/ide@3/disk@0,0:a
ok setenv boot-device disk backup_root net
ok nvstore

Adding new hard drive (old and new way)

2008-02-19T10:54:00.002+02:00

In x86 Solaris 10 it is possible to add hard drive in 2 ways, lets begin with old one.

1. Add new hard drive.
2. Boot server and run :
#drvconfig
#disks
3. Issue :
#format
Output must be a list of all configured drives.

New one:
1. Add new hard drive.
2. Run:
#devfsadm
3. Check results with format command.

Drive is recognized, but it's necessary to make slices and filesystems to use it.

Creating Solaris packages.

2008-02-18T15:17:00.006+02:00

Procedure of creating packages for Solaris is quite trivial, it is done in several steps:

1.We must install program on our test system.
2.Create file which includes paths to all files which will be installed.
Lets name it files. Assume that you have installed apache web server in /usr/local/apache directory then you can do this:
%cd /usr/loca/apache
%find . -print >/tmp/files.
3.Create prototype file which will describe permissions and type of each file in a package.
% cat /tmp/files | pkgproto > /tmp/Prototype
4. Now it's time to make scripts which will do preparation/cleaning job during package installation and/or removal.
They has self describing names:
preinstall,postinstall,preremove,postremove,checkinstall,request,depend.
Of course it is not mandatory, package can be without these files.
5.Create pkginfo file it will look like this:
PKG="Apache"
NAME="Apache"
ARCH="sparc"
VERSION="1.3.14"
CATEGORY="application"
VENDOR="Unixinmind ltd"
EMAIL="nonexist@nowhere"
PSTAMP="Oleksii Dzhulai"
BASEDIR="/usr/local/apache"
CLASSES="none"
It will be used by packaging system.
6. Include scripts and pkginfo file to Prototype, it will be something like this:

i ./pkginfo
i ./preinstall
d none bin 0755 nobody nobody
f none bin/httpd 0755 nobody nobody
f none bin/ab 0755 nobody nobody
....

7. Run:
pkgmk -o -r /
This command creates package file structure in /var/spool/pkg/Apache.
8. To convert package to stream format:
pkgtrans -s /var/spool/pkg /tmp/Apache-1.3.14.tar

Package is ready!!

For more information:
http://docs.sun.com/app/docs/doc/817-0406

What is the price of using md raid in perfomance matter.

2007-02-09T09:18:00.001+02:00

Shown tables are generated by bonnie on md level 0, level 1, and directly on device.


            -------Sequential Output------ --Sequential Input-- --Random-
            -Per Chr- ---Block-- -Rewrite- -Per Chr- ---Block-- --Seeks--
Machine        Size K/sec %CP  K/sec %CP K/sec %CP K/sec %CP  K/sec %CP  /sec %CP
md_1             4G 29434  97  60303  47 26859  13 31448  97  63791  19 430.1   1
md_0             4G 28963  97 106220  79 51660  28 31390  98 127605  41 421.3   1
direct           4G 28530  95  60638  47 27528  13 31255  97  63966  18 280.9   1

                         ------Sequential Create------ --------Random Create--------
                         -Create-- --Read---  --Delete- -Create-- --Read---   --Delete--
      files:max:min       /sec %CP  /sec %CP   /sec %CP  /sec %CP  /sec  %CP   /sec %CP
md_1      100:100:0         4398  83 87013  99  14563  70  3748  89  99414  99  13564  71
md_0      100:100:0         4214  91 93285 100  16189  83  3999  91 108003  99  16596  90
direct    100:100:0         4193  83 89778  99  15138  76  4015  91 101260 100  14435  78

Superficial performance testing of Linux production file systems.

2007-02-08T15:16:00.001+02:00

I saw benchmarks on official sites, but I like to examine myself.
So I ran bonnie++ tests on ext3/ext3 (data=journal), XFS, JFS, ReiserFSv3.

Hardware doesn't matter as it is the same.
Kernel 2.6.18.

bonnie -u root -d /data -s 4G -n 100:100k:10k:5000 -x 2

                    ------Sequential Output------ --Sequential Input- --Random-
               -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
FS             Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
ext3             4G 29434  97 60303  47 26859  13 31448  97 63791  19 430.1   1
ext3_jrn         4G 13556  46 21666  18 17691  11 31078  96 63742  19 474.1   2
xfs              4G 32877  98 60393  24 27376  12 31351  97 64273  18 523.5   1
jfs              4G 30539  92 49633  21 27222  10 31149  97 59524  18 446.0   1
reiserfs3        4G 32412  97 61730  39 26794  14 29512  95 63295  23 458.7   2

               ------Sequential Create------ --------Random Create--------
               -Create--  --Read--- -Delete-- -Create-- ---Read--- -Delete--
files:max:min        /sec %CP   /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
ext3      100:100:0  4398  83  87013  99 14563  70  3748  89  99414  99 13564  71
ext3_jrnl 100:100:0  2300  48  93241  99 14068  69  1906  43 107315  99 13250  71
xfs       100:100:0  1405  31  65728  96  1195  19  1204  25  62579  96   213   4
jfs       100:100:0   597   0 110141  99   472   0   223   0 102004  98   201   0
reiserfs3 100:100:0  4524  70  89320  87  2416  25  4095  66 104493  99  1033  14

Memcached as a storage for PHP sessions

2007-01-30T20:07:00.001+02:00

Two ways how to make PHP store sessions in memcached.

By mean of writing own arguments for session_set_save_handler().

Advantages: much simple to deploy, exists some working samples.
Handicaps: all existing projects need to be customized, I mean that in all scripts where we make "session_start" we have to include our file with declarations.

By the way of writing PECL module.

Advantages: such method can be absolutely transparent for projects.
Handicaps: needs good understanding of PHP API.

Bricks of the knowledge wall

GUDS is what Oracle can ask you

SLAMD!

Default and permited projects

The cruel trooth abou fssnap

Simplest iscsi configuration in a minute

Sun Java Console Timeout

Don't waste pure man's RAM

Bluetooth gprs internet in several steps.

Check content of the IPS packages

Grub difference

Beadm usage examples

SMF Contracts or how to find out what FMRI the process uses

Solaris memory measurement

Watching Sun Cluster's binary logs

Jumpstart boot process

Sun Cluster Console

Simplest way to mount CDROM

Resource pool zone assignment.

Users notification about subversion commits(the most scallable way).

How to find out what mode Solaris can use on your hardware 64 or 32?

Share ZFS dataset through CIFS/Samba

Autofs and auto mounted homes.

Cacaoadm and SUN Directory Server 6.3.1

Configuring SMF Service Probes for Containers in Sun Cluster 3.2.

How to find recently added FC disks

Generate sshd server keys

Turning on Sun Cluster checks debug

Resetting root password on Solaris

Simple upgrade with Liveupgrade

Persistent static routes

Appeared in Solaris 10 update 3

Solaris extended accounting tips

Command list for work with projects/tasks in Solaris

Solaris Resource Pools (moving cpus)

Sybase SMF scripts

The fastest way to create long term ssl certificates for SUN Directory Server 6.3

VLV indexes creation

Moving solaris zones between different hosts

Using Solaris JumpStart With the Solaris 10 OS for x86/x64 Platforms

Ssh and nscd

How to examine content of certificates database

Sun Directory Server backup scripts

Solaris native LDAP client(Password policies)

Solaris native LDAP client(using netgroups)

Less known Solaris features

Some tips using ssl with Sun Directory Server 6.3.1

Webconsole on all interfaces

Export of rbac databases to ldap

Importing Projects database to LDAP

projects Database

Files you have to import to LDAP for Solaris client proper work

Solaris LDAP client setup. part 2(management interface)

Solaris LDAP client setup. part 1

Postinstall configuration of Solaris zone

First steps to have Sun One Directory Server up and running

Sun One Directory Server installation

Installing zone support on basic Solaris 10 system

First steps to do after fresh installation of Solaris 10(core system) part 1

First steps to do after fresh installation of Solaris 10(core system) part 1

From Debian with love!

Debian way of Solaris

Quick view at Solaris 10 10/08 Release

Good article about Mysql Cluster deployed in Solaris Zones

Some usefull shell tricks

Reuse previous arguments

Manage directory navigation with pushd and popd

Using X server in Windows for calling remote graphical applications in Unix

Enabling shared folder in Citrix Metaframe client

Check what package a file belongs to.

Linux kernel interactive map

Solaris 10 networking configuration tips

sys-unconfig

Do not confuse with configuration files of NFS in Solaris.

Solaris Soft Partitioning

What is new?

Creating Soft Partitions

Extent Headers

Mirroring Soft Partitions

Combining Soft Partitions Together into a RAID5 Device

`projects` Database