Timeline for sudo command after long sleep call without re-prompting sudo password
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 12:04 | history | edited | CommunityBot | Commonmark migration | |
| Aug 26, 2013 at 0:21 | answer | added | Gilles 'SO- stop being evil' | timeline score: 7 | |
| Aug 23, 2013 at 12:52 | comment | added | Bratchley | Have you looked into modifying the timestamp_timeout default value in sudoers? You should be able to alter the timeout on a per-user basis. | |
| Aug 23, 2013 at 11:36 | answer | added | Ulrich Schwarz | timeline score: 3 | |
| Aug 23, 2013 at 10:04 | comment | added | Drav Sloan | If you do go down the NOPASSWD route, you may want to use sleep $(bc <<< $1*60) && sudo pm-suspend instead, so that if you Ctrl-C the function it wont run pm-suspend (and you can cancel it from suspending your OS). | |
| Aug 23, 2013 at 9:48 | vote | accept | buren | ||
| Aug 23, 2013 at 9:38 | answer | added | Matt | timeline score: 3 | |
| Aug 23, 2013 at 9:12 | review | First posts | |||
| Aug 23, 2013 at 9:14 | |||||
| Aug 23, 2013 at 8:57 | comment | added | Mat | Why don't you simply authorize that command without a password in sudo's config? | |
| Aug 23, 2013 at 8:55 | history | asked | buren | CC BY-SA 3.0 |