Interesting to note that strace is actually changing the output of crontab -e in debian 4.0 (perhaps by calling isatty somewhere?), just not the return value. So it could be that a bug with crontab -e returning the right value was fixed in the 2008-2010 timeframe instead of a bug being introduced then.
[email protected]$ export EDITOR=cat ; crontab -e >/dev/null ; ret1=$? ; echo === ; strace -o/dev/null crontab -e ; ret2=$? ; echo ; echo return: $ret1, straced return: $ret2 ; cat /etc/issue No modification made === crontabs/ski: Permission denied return: 0, straced return: 0 Debian GNU/Linux 4.0 \n \l [email protected]$ export EDITOR=cat ; crontab -e >/dev/null ; ret1=$? ; echo === ; strace -o/dev/null crontab -e ; ret2=$? ; echo ; echo return: $ret1, straced return: $ret2 ; cat /etc/issue No modification made === /var/spool/cron/crontabs/ski: Permission denied return: 0, straced return: 0 Debian GNU/Linux 5.0 \n \l [email protected]$ export EDITOR=cat ; crontab -e >/dev/null ; ret1=$? ; echo === ; strace -o/dev/null crontab -e ; ret2=$? ; echo ; echo return: $ret1, straced return: $ret2 ; cat /etc/issue No modification made === crontabs/ski/: fdopen: Permission denied return: 0, straced return: 1 Debian GNU/Linux 6.0 \n \l -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/582319 Title: strace crontab -e bombs on 10.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strace/+bug/582319/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
