service(8) to Solaris SMF command lookup

If as a Linux native you find yourself on a Solaris box, you'll noticed that from Solaris 10 SYS V rc-style scripts are no longer used to control daemon processes. Instead, the SMF system is used. Below are some service(8) commands and their Solaris counterparts: <blockquote> service httpd restart || svcadm restart httpd service --status-all || svcs -a service httpd --full-restart || svcadm disable -s httpd && svcadm enable -s httpd </blockquote> A word about "service names" under Solaris SMF. They are not so much names, more patterns matching an identifying path-like string (or FRMI in the lingo). There may be more than one service that matches the pattern, httpd, in this case. "dns" is one such example, as it matches the services: <blockquote> svc:/network/dns/client:default </blockquote> <blockquote> svc:/network/dns/server:default </blockquote> both. In this case, you have to increase the pattern until there is only one unique match: svcadm restart dns/server for example. For a fuller explanation, see:<a href="http://www.sun.com/bigadmin/content/selfheal/smf-quickstart.jsp"> http://www.sun.com/bigadmin/content/selfheal/smf-quickstart.jsp</a>

2010-03-08T17:38:10Z

2010-03-08T17:38:10Z

History expansion, much like the command <blockquote> cd - </blockquote> which moves you into the directory that you were in immediately prior to the current one, is an oft-overlooked but powerful and convienient mechanism for making your time in the shell more accurate, and for saving time. The simplest form of this is: <blockquote> $ grep -i somestring somefile $ mv !$ /tmp </blockquote> This will search the file somefile for the string somestring, and then move somefile into the directory /tmp. Another common usage is the "quick substitution" command: <blockquote> $ echo somefile $ ^echo^cat^ </blockquote> This will echo the word "somefile" to STDOUT. The '^^^' command will execute the previous command, substituting the first parameter (echo) for the second (cat) - in this instance attempting to cat a file called somefile. The HISTORY EXPANSION section of the bash(1) manpage details further modifiers, all in the same vein as vi commands, that can be used to further modify or search the command history.

2010-03-02T11:09:57Z

http://moourl.com/q5lz6

History expansion in bash shell

2010-03-08T16:57:25Z

I’ve been using a couple of nice shell aliases when working with ad-hoc iptables rules. You can spruce them up as a batch file, but they’re fine for me as a quick and dirty way to manipulate rules. <blockquote>alias ips="/sbin/iptables --line-numbers -vn -L INPUT | grep -i"alias ipd="/sbin/iptables -D INPUT"</blockquote> That’s all there is to it. You can then interrogate almost any aspect of the default INPUT filter with: <blockquote>ips icmp</blockquote> <blockquote>ips 10.64.0</blockquote> <blockquote>ips drop</blockquote> to view all ICMP rules, any rules relating to the 10.64.0 subnet, or all rules that drop packets. The way I use these together, and the reason that `ips` includes the –line-numbers argument, is that I like to add rules and then easily delete them with: <blockquote># ips 19230 0 0 DROP all -- * * 192.0.2.0/24 0.0.0.0/0</blockquote> <blockquote># ipd 30</blockquote> using the rule number as an easier way of deleting the rule without having to conjour up a matching rule specification.

2010-02-26T15:04:00Z

http://moourl.com/pm261

Easily manipulate iptables rules with aliases

2010-03-08T16:57:23Z

The bash shell has a powerful history mechanism, which in its default state isn't too useful. Luckily the modifications are quite easy to make. Hit Ctrl-R and then type the first few letters of a previously executed command. Bash will search through the search history to find the command that matches this string. Continue to hit Ctrl-R to see the alternatives. When you find the command that you want, hit return and it'll be executed. Fewer keystrokes, less effort, fewer typos. The bash(1) manpage details a number of variables that dictate how bash handles command history. Two of these variables are: <blockquote> HISTFILESIZE </blockquote> <blockquote> HISTSIZE </blockquote> Both have a default of 500, which if live on the command line is far too small. Increase the size of both of these variables by adding the following lines to your $HOME/.bashrc file: <blockquote> export HISTFILESIZE=20000 export HISTSIZE=$HISTFILESIZE </blockquote> A pool of 20,000 previously executed commands (or more if you fancy) increases the utility of the command history search dramatically. Advanced shell users might like to take note of what the manpage says about the $HISTCONTROL variable, especially the sentence: <blockquote> If the list of values includes ignorespace, lines which begin with a space character are not saved  in the history list. </blockquote>

2010-02-27T13:39:31Z

http://moourl.com/o9btn

Fewer keystrokes in bash with Ctrl-R

2010-03-08T16:57:23Z

To display the top 10 consumers of memory: <blockquote> <code>ps -auxf | sort -nr -k 4 | head -10</code> </blockquote> To display the top 10 consumers of CPU: <blockquote> <code>ps -auxf | sort -nr -k 3 | head -10</code> </blockquote>

2010-02-26T10:18:42Z

http://moourl.com/3w5ul

Using ps to find the top 10 consumers of CPU and memory

2010-03-08T16:57:22Z

Hopefully you will be using <a href="http://www.sun.com/bigadmin/content/selfheal/smf-quickstart.jsp">SMF</a> to manage the services. You will doubtless know that the command <blockquote> svcadm restart domain1 </blockquote> would restart a domain. However, if you want to script your restart like this: <blockquote> svcadm restart domain1 && touch .reload </blockquote> perhaps, the the return code you are checking is a result of the restart command being sucessfully passed to the SMF facility. If you really want to wait for the domain to restart properly, the do then following: <blockquote> svcadm disable -s domain1 && svcadm enable -s domain1 && touch .reload </blockquote> The -s switch svcadm waits for the result of the termination, and sets its return code appropriately. Likewise when starting the domain.

2010-02-23T15:19:33Z

http://moourl.com/f0zys

Restart Sun/Oracle Glassfish domain on Solaris 10 under SMF

2010-03-08T16:57:21Z