Ah, underfull and overfull hboxes and vboxes in latex.....
You can do certain things:
a) if they look fine - disregard those warnings
b) for overfull/underfull hboxes, you need to rewrite the line that has the problem (latex will report it), or resize the figures (if they are the cause) accordingly
c) for overfull/underfull vboxes - you need to either allow some flexibility in the interline and/or interparagraph spacing (e.g, give \baselineskip, \lineskip, and
\parskip some stretchability), or else tell LaTeX that you want \raggedbottom pages. Underfull boxes are a consequence of not enough flexibility in the vertical spacing, and lines that don't happen to exactly fill the page size. Just type \raggedbottom at the beginnning in the preamble, and that should cure underful vboxes.
Wednesday, November 15, 2006
Monday, November 13, 2006
Kill by name!
This is an extremely useful command that I use all the time.
I assume everyone is familiar with the linux "kill" command.
For whatever reason, I had started 10 instances of a command named "xycommand". And, now I want to kill all the 10 instances.
If I wer using "kill", I would have to first do a "ps | grep xycommand" to identify the process ids, and kill each instance separely.
An efficient way of accomplishing the same is to use the "killall" command.
Thus,
$killall xycommand
kills off all the instances with the name xycommand.
I assume everyone is familiar with the linux "kill" command.
For whatever reason, I had started 10 instances of a command named "xycommand". And, now I want to kill all the 10 instances.
If I wer using "kill", I would have to first do a "ps | grep xycommand" to identify the process ids, and kill each instance separely.
An efficient way of accomplishing the same is to use the "killall" command.
Thus,
$killall xycommand
kills off all the instances with the name xycommand.
Sunday, November 12, 2006
ps pissing you off?
The linux "ps" command is very useful as we all know. However, it just pains me when it strips off the larger commands.
Thus if you wanted to do something like
ps aux | grep "xxcommand"
it will only grep through the length that is fitted in the screen.
Thus if you have a command like the foll., no matches will be found:
xxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxcommand
What is the workaround? Use --columns along with ps to specify the number of columns that is outputted. Normally it defaults to tthe number of columns in the terminal leading to the above problem.
e.g.
ps aux --columns=1000 | grep "xxcommmand" ....and your o/p will be what you are seeking.
Peace with ps...
Thus if you wanted to do something like
ps aux | grep "xxcommand"
it will only grep through the length that is fitted in the screen.
Thus if you have a command like the foll., no matches will be found:
xxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxcommand
What is the workaround? Use --columns along with ps to specify the number of columns that is outputted. Normally it defaults to tthe number of columns in the terminal leading to the above problem.
e.g.
ps aux --columns=1000 | grep "xxcommmand" ....and your o/p will be what you are seeking.
Peace with ps...
Subscribe to:
Posts (Atom)