|
I guess one other thing to say about this,
which I only imply below, is that I use this kind of stuff on an installation
with CentOS with a slightly older kernel and it all seems to work fine, so it
seems to have something to do with the Ubuntu configuration that is killing
me. I also installed the Java and Ant trees directly from the server that
works using scp –r, so those are the same. xc From: Xeno Campanoli
[mailto:xcampanoli@real.com] Well, that last statement wasn’t
quite accurate. The example statement I give does in fact fail.
I’m not sure why. However, when I use <exec
executeable=”/bin/date” failonerror=”true” />, it
gets past the statement, but I get no output. My ant version is 1.6.5,
and I’m using j2sdk1.4.2_09. xc From: Xeno Campanoli
[mailto:xcampanoli@real.com] I installed Ubuntu for my development server recently
because getting CentOS was such a royal PITA, and it’s all gone very
nicely except for one thing: <exec> task is failing on my in some
very inconvenient circumstances. It all started when I discovered that
most of my circumstances where I was execing “echo” were
completely failing. This was easy to fix by using the “echo”
task itself. Now I’m finding some ruby programs I very much need to
work are failing when exec’ed. Running “/bin/date”, for
instance, as a sanity check, results in nothing at all. I run: <exec executable=”/bin/date”
failonerror=”true”>
<arg line=”>/tmp/mess888.lst” /> </exec> Results in nothing; no failure; no output. Can anyone make some suggestions? This is a real
disaster if it won’t work. Sincerely, Xeno xc Breezy Badger Ubuntu root access: sudo passwd;su - Truth before Power! |