-
Notifications
You must be signed in to change notification settings - Fork 119
Add support or documentation for "timestamp_timeout = 0" scenario #13
Comments
Are you on OS X? Are you getting Would you be able to find out if there is any way to detect whether the sudo timestamp timeout is 0? If so, we could fall back to another version of |
Yes, I'm on OSX 10.10.4. I looked around and I'm not seeing a way to check the current sudo timeout. The value is set in It may be possible to tell sudo to use sudo-prompt's Will investigate this further when I have more time. |
I have been thinking about it some more. I will try to rewire
This will give the best of both worlds. A sudo session which endures across multiple commands if possible, and support for systems with the sudo timeout set to 0. It will take me some time but I hope to get started on it soon. |
Have been struggling with getting sudo-prompt to work, and finally figured out why. My environment's timestamp timeout was set to 0. This resulted in
attempt()
's check of theif (/sudo: /i.test(stderr))
condition always matching, and throwing an error on the second command execution.It would be nice if there was either a) a workaround, or b) a check for this condition within sudo-prompt and subsequent user notification.
The text was updated successfully, but these errors were encountered: