This will cause KBACKUP to run in ``tty-mode'', not using the dialog(1) program, while still offering full functionality. Generally this will not be needed, but it might be helpful in debugging (e.g. using script(1) ), for porting it to other systems but Linux and for creating a boot disk without the rather big dialog(1) binary.
If dialog(1) is not installed on your system, KBACKUP will detect this and automatically start up in ``tty-mode''.
Well, in fact, there are some other options, but they are not meant to be used by you. In order to recognise what to do when called in scheduled operation mode, atrun(8) calls it with some options. You might, however , use them to perform a scheduled operation if your at(1) /crond(8) does not work. Have a look at the source to see what they do.
(e.g. kbackup -scheduled-backup .-scheduled-1234 to perform the scheduled backup number 1234)