mmm .. not sure I follow. The issue is only for the scheduler to be able to get the daemon process started EXACTLY AS IF IT WAS THE USER WHO STARTED IT (complete with user-console for stdout reporting).

It works fine already when started by a user, who may cancel continuation on the basis of feedback on display in the console .. ie via stdout.

A similar process is also schedule-run in the background with Carp'd logging -- but that, of course, does not permit the stdout-interactivity in a console that provides the cancellation opportunity required here.

Ideally maybe a more sophisticated cron-tool would provide this functionality, but that does not seem to be on the horizon, and I just wondered if it could be achieved from the inside so to speak?