I have a weird problem with editing cron jobs on a Suse 11.1 box.

When logged in as a user, I type crontab -e and am immediately welcomed by a message saying the process has stopped. Killing the process requires me to be root and to issue a kill -9 <pid>.

There's no cron log in /var/log. There's no entry in /var/log/warn and /var/log/messages just has an entry saying that editing is beginning.

I can sometimes successfully run crontab -e as a user (and nearly always as root), but only once - subsequent attempts fail.

All users have Bash selected as the editor.

Any thoughts?

Bash isn't an editor. What's $EDITOR ?

Slip of the tongue - the editor's Emacs. No other problems with that - I can edit files fine and, like I said, crontab -e works sometimes. Now I'm getting the problem with the root account, too.