Time to schedule some tasks!
First you need to make sure your in the /etc/cron.d/cron.allow file. If you are not SU to root and add yourself into it.
Now to create your new crontab file;
crontab -e
You are in vi in your newly created crontab file (note if you do not have access to do this it will say so)
Now, i’m no expert at using vi, but if you press i you will go into insert mode. Do this, then type the cron job details. A typical cron job will look like this
Oh no. I’ve managed to get this error before. And it was right after i applied compression to the rpool zfs filesystem. Upon the next reboot i was greeted with this error message;
Error 16 : Inconsistent filesystem structure
For me it was a show stopper and i had to go into recovery. So i’ve learnt my lesson - Not to touch the rpool zpool.
I was lucky enough to have put my data within a zfs filesystem (rpool/virtual) i created within the default rpool zpool. I use this spot for my VirtualBox virtual machines.
I’ve had a play with WHS but eventually got annoyed with its lack of performance. Yes i know its not built for performance and typically is used just as a backup / simple store with duplication as redundancy, just i couldn’t stand the speed of the thing. If you were ever unlucky enough (even post power pack 1) to do a copy during the “data moving” the performance was even worse. On a positive note nothing beats it if you have a heap of non-similar sized disks that you want to put together (with redundancy) as a single shared storage pool.
ZFS compression as of OpenSolaris 2008.11 has a few types to choose from.
lzjb (default) | gzip | gzip-[1-9]
They are used via the zfs set compression=gzip poolname command.
The following test was quickly done out of personal interest - and is in no way scientific!
I have a AMD cpu with 3 cores (2.4Ghz). The data i copied to each of the shares consisted of video / documents / pictures and music. The first test i have done is based on compression only (i have not measured throughput)
There are two ways to setup the auto login for OpenSolaris (2008.11);
One - You can fire up the GUI using gdmsetup. Update : this didnt actually work when i tried it recentely - it might not be in this release of opensolaris.
Two - go to /etc/x****11/gdm/custom.conf (in newer releases its just /etc/gdm/custom.conf) and manually modify the required fields in the [daemon] section and add the following;
[daemon] AutomaticLoginEnable=true AutomaticLogin=username
So… i’m looking for a way to fire up some VirtualBox machines after a reboot on OpenSolaris. SMF is the key. Just need to create some XML docs that fire up a couple of headless vm’s.
Shouldn’t be too hard. Lets see what i can come up with.
Here is a good pdf about migrating Legacy RC services into SMF, which has given me a few pointers….
how to shutdown a vm;