|
|
|
|
|
|
by mike_hock
12 days ago
|
|
|
> How is this different? Any way you slice it, you have to configure it somewhere if you're not lucky enough for the default to be acceptable. It's a workaround for a design flaw. If you forget it you'll notice when it fails in production. There should rarely be a need to change the default path (just specify the full path if necessary), it should just be the same when you test and when it runs by itself. Trigger on demand would of course solve that. > exactly the same ("the time spec is too complex") Of course, the timespec complaint is bullshit. Both have manpages that will tell you immediately if you don't have it memorized. |
|
|
That's what I'm saying though; how is it a design flaw? It's arguably a flaw in the default configuration. That's certainly fixable without changing the design at all.
> Trigger on demand would of course solve that.
Is it a design flaw that you can't trigger the job as a test? No, that's just a missing feature.