Dylan Penhale wrote:
Our JOBTITLES have been getting longer and longer, and it's not really
practical to shorten them as we have quite a few scripts that use their
format. I have been modifying the rush.conf file in an attempt to adapt
the TITLE column to accommodate this increase. (currently about 65 chars
seems sufficient).
I read the REPORT FORMATTING disclaimer and admit at being far from a
Perl master, but I have a simple question. In the following example
could you tell me why rush -laj displays a 65 char column width (in both
shell and iRush) and yet rush -lj does not?
Some commands (rush -laj) do their formatting on the client side,
and some commands (rush -lj) do their formatting on the job server side.
For your -lj mods to take effect, you must tweak the rush.conf file
on the job server, and the jobserver's daemon will have had to reload
the rush.conf file (do a 'tail -f /usr/local/rush/var/rushd.log'
to watch for the 'rush.conf file reloaded' message) before your -lj
changes will take effect.
Once satisfied with the changes, be sure to push the rush.conf file
to all machines.
I have tried restarting rushd. Also have pushed the rush.conf file out
network wide.
Hmm, make sure you're manipulating the rushd that is the jobserver
for the job you're looking at.
eg. if the job you're looking at is 'tahoe.123' (eg. rush -lj tahoe.123)
then make sure you've tweaked the rush.conf file on host tahoe, and
are sure tahoe's rushd has reloaded the rush.conf file.
Is it posable that rush -lj has a limit of around 55 chars? and rush
-laj doesn't?
No, there should be no such limitation like that.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|