tag:blogger.com,1999:blog-17885055.post190748834219167977..comments2009-09-25T14:43:29.275+02:00Julio Merinohttp://www.blogger.com/profile/08233346614736256024noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-17885055.post-74923301342812557652009-09-25T14:43:29.275+02:002009-09-25T14:43:29.275+02:00Looks like I didn&#39;t make it clear. Yes, the system administrator can change the default, but I don&#39;t want to.<br /><br />You certainly don&#39;t want to raise the timeout to many hours (covering the longest possible compilation that you&#39;ll do), as doing that is almost like not setting any timeout at all. So running the command I shown is only a temporary measure for a specific situation without having to change the defaults.Julio Merinohttp://www.blogger.com/profile/08233346614736256024noreply@blogger.comtag:blogger.com,1999:blog-17885055.post-39700823809060221892009-09-24T14:18:22.990+02:002009-09-24T14:18:22.990+02:00Excuse me, but you, as a BSD developer,<br />please can’t tell me you didn’t RTFM<br />for about three minutes – sudoers(5) –<br />to discover the timestamp_timeout op-<br />tion, right? Please say it isn’t.<br /><br />Your workaround is really more of a<br />würgaround and certainly doesn’t help<br />in getting sudo accepted more widely.<br /><br />Just sudo visudo, then add lines like<br />this ↓ then save and exit. This will<br />give you unlimited timeouts. (Note: on<br />e.g. Kunterbuntu systems you’ll also<br />need to disable tty tickets.)<br /><br />Defaults passwd_timeout=0<br />Defaults timestamp_timeout=-1mirabiloshttps://launchpad.net/~mirabilosnoreply@blogger.com