 Questions and
Answers
Amy Rich
Q I'm migrating from Solaris 8 to Solaris 9.
I use JumpStart to install all of our machines with 10MB of space for the replica
databases. I kept the same configuration when moving to Solaris 9, and it told
me that there was not enough room for the state databases. Obviously things
have changed, so I'm wondering how much space I should be allocating for that
slice now.
A With the version of Solaris Volume Manager
(called SDS in older releases), Sun recommends 100MB for the slices containing
the replicas. In Solaris 8, each replica occupied 1034 disk blocks of the partition.
With the new version of SVM, the default replica size is 8192 blocks, eight
times the size of those in Solaris 8. If you are upgrading to SVM from SDS,
be sure to increase the replica slice size. If you keep the slice size the same
and then remove a default-sized SDS replica and add a new SVM one, you'll likely
overwrite the blocks of the filesystem located after your replica slice. You
can specify the size of a replica by setting a length when invoking metadb:
metadb -l length_in_blocks
Q Our sendmail 8.12.11 server handles mail for a
domain that belongs to someone else. If this user's machine is up, he wants all
mail delivered to it. If his machine is down, he wants all of the mail for his
domain delivered to a username on a different machine. Can you provide a custom
ruleset that would do what he's after?
A Let's say your user's domain is client.domain,
his machine is host.client.domain, and this other email address is user@other.domain.
You can create a mailertable entry that will deliver his mail as desired.
|
