I wanted to corroborate an observation:
When I attempt to run dsmc on a box with no dsm.opt, it presents me
with a "warning" about the omission, and soldiers on with running the
program.
When I attempt to run an incr from the scheduler, though, I get silent
failure.
Simply 'touch'ing the dsm.opt file (i.e. a zero-size file, no
directives) permits the scheduler process to run normally, and of
course obviates the warning at the command line.
This was on an ubuntu box, Karmic, I think.
Does this match your-all experiences? If so, I'm going to go do the
PMR thing. It's silly that a warning condition should do this.
- Allen S. Rout
|