Bugzilla – Bug 186
sudo crontab -e -u far3941 causes screen to roll and never return
Last modified: 2005-10-28 16:37:54 MDT
On Unix OS of MP-RAS Version 3.03.00.03 the command of "sudo crontab -e -u far3941" will cause the screen to continually roll with the following two lines: : At EOF The screen will not stop and you are required to exit the session to stop this. This is reproducible on sudo 1.6.8p6 and 1.6.8p8. I can send a core file produced on sudo 1.6.8p6, but for some reason, the 1.6.8p8 will not create a core file. This is requiring a work around of making the user "sudo su - far3941" to temporarily get around this and edit the crontab for the user. MP-RAS Version 3.03 is a change from the MP-RAS Ver 3.02 where 3.02 uses the metaware C Compiler and the 3.03 uses the GNU C Compiler. I had to midify the config.guess file with the following information on line 1044 to allow configure compile to see the mp-ras ver 3.3: | 4400:*:4.2:3.3 | 4850:*:4.2:3.3 | SKA40:*:4.2:3.3 | S7501HG0:*:4.0:3.0 | S7501HG0:*:4.2:3.3
This doesn't sound like a sudo problem, it sounds like the value of the EDITOR or VISUAL environment variables is the issue. You should compare the value of those variables (for instance with the printenv command) in the environment of the user running sudo to their value when "su - far3941" has been run. Also look for differences in editor-related variables (such as EXINIT for vi).
Installed sudo 1.6.8p9 and this problem dissappeared. You can close this incident/bug report. All the settings before and after, the install, for the editor are the same. This was not a settings issue. based upon what you had requested below: [This doesn't sound like a sudo problem, it sounds like the value of the EDITOR or VISUAL environment variables is the issue. You should compare the value of those variables (for instance with the printenv command) in the environment of the user running sudo to their value when "su - far3941" has been run. Also look for differences in editor-related variables (such as EXINIT for vi).]
Closed at submitter's request.
I have just completed the installation of sudo 1.6.8p9 This patch level did not have the problem. This bug request can be marked as completed by virtue of the installation of the nest patch level.