On one of my web servers I use the “-Xrs” parameter in the JAVA_OPTIONS on a Solaris server. This tells the JVM to ignore any system shutdown requests. This prevents the JVM from shutting down in the event there is a system panic which may not otherwise cause a system crash. See the JVM parameters page for Solaris for more details.
Sometimes when attempting to grep through the files in a directory, there are so many files in the directory that grep returns an error indicating the argument list is too long. Fix this by using xargs.
find ./ -print | xargs grep -l <your_string>
ls -1 | wc -l
This is any easy one, but I always forget the syntax and have to look in one of my scripts…
To start a WebLogic managed server from the command line, in the domain bin directory – on the physical server where the managed server resides – do:
nohup ./startManagedWebLogic.sh <managed_server_name> t3://<admin_server>:<admin_port> &
I am working with an installation of Solaris 10 on a VMWare virtual machine. After the initial installation, the system was indicating that the nodename was unknown. Additionally, the network configuration is not configured properly yet, so the server is not able to reach the DHCP host for hostname assignment. To fix this issue, I had to do a little poking around. I asked my good friend Mr. Google, and that turned up a blog called markwilson.it, and an entry about the issue which points me to the Sun Developers Network post on the issue.
The short solution is that you must create a file called “nodename” (no extenstion) in the /etc directory. Inside the file, insert one line with the nodename you would like to use. Reboot.
Additional assistance for configuring Solaris 10 DHCP client to register with a Microsoft DNS is found on the same blog. See also, SUN’s instructions for the Solaris 10 DHCP to DNS configuration.