cron executable

[Alex Glennie]

if dtpad fails .... try dtterm,xterm or hpterm

[Patrick Wallek]

>>try dtterm,xterm or hpterm

I'm not sure what that would accomplish, other than just opening a terminal window.

I tried setting EDITOR=xterm on a Linux system and it did not work well. It opened a new xterm window, but the crontab file did not show up in an editor, which is about what I would expect.

I set EDITOR=gedit and then did a 'crontab -e' and the gedit editor opened and functioned quite well with the crontab file.

I would expect dtpad to work. You may need to give the full path to dtpad if it doesn't work with just EDITOR=dtpad.

[Alex Glennie]

Donald ignore earlier post.

How or rather what are you running under exceed ? in otherwords are you logging into CDE, running a command via a terminal session or something else ?

within the terminal window type echo $TERM ?
result ?
export TERM=dtterm
try a crontab -e ?
result ?

If you can login via CDE let me know I'm more familar with that interface but have an old version of Exceed if needed if I boot into windows. currently uncertain if this is a bug or an issue with exceed/unix settings ....

[Alex Glennie]

Patrick,

Totally agree .... moment of madness

[Donald Thaler]

dtterm worked... thanks to all...

i'm using exceed v10 with their secure shell v10 ...i'm guessing that in the command option that looks like "/usr/dt/bin/dtsession &", i need to add EXPORT=dtterm

[Donald Thaler]

ooops it was dtpad that worked...

[Steven Schweda]

> [...] i need to add EXPORT=dtterm

> ooops it was dtpad that worked...

And it wasn't "EXPORT=", either. You (and
your readers) might profit if you explored
the benefits of using that newfangled
copy+paste technology. As the eminent
Abraham Van Helsing once said, "[...]
knowledge is stronger than memory, and we
should not trust the weaker." Or as an
automotive expert on NPR once said, "If you
don't think too good, don't think too much."