I stumbled across a limitation feature behaviour of Solaris over the weekend – by default it only allows you to run a maximum of 100 cron jobs at once. I suppose this to protect against “shooting oneself in the head”, but aaaarghhh. Reminds me why I love Monday mornings.
Scenario: the current Solaris Sparc system is booting off a single UFS disk (eg when cloned from an image).
Sometimes when connecting into a Solaris box via multiple jumps eg Citrix to putty to jumphost to target host, the terminal can get confused about screen size and scramble the output.
A useful [script ][1]from BigAdmin for increasing the size of a tmpfs /tmp without rebooting.
The latest edition of the venerable [UNIX and Linux System Administration Handbook]1 has a good section discussing the “RAID5 Write Hole”:
A work colleagues used an interesting technique to rapidly build some Solaris systems. We usually use Jumpstart but due to the large number of identical systems to be built, he had to use a faster method.
An example of Solaris IP Multipathing, for future reference:
Or, after RTFM’ing, an easier way: [SunDocs Recovering ALOM passwords][1]:
When creating a new Solaris zone, one of the steps involves connecting to the zone’s console for the initial configuration:
When running the ps command on Solaris, the output is truncated at 80 columns – really annoying when the command line to start up a process (typically a daemon) is really long.
Solaris has a feature called [RBAC][1], that allows you to provide role-based security (I believe this is similar to [SELinux][2]).
How to connect to a Cisco device (or other serial devices) using OSX and a USB to Serial converter (eg ATEN).
Firewalling on Solaris 10:
Quick notes; [see Solaris: Logging to a separate loghost, the easy way][1].