upas/fs: remove read timeout via alarm(2) in pop3resp
The alarm note is not handled by upas/fs, so if and when it did fire, the pop3 client process would terminate rendering the entire fs unresponsive.
This commit is contained in:
parent
c35f95de2a
commit
d7aa56c073
1 changed files with 0 additions and 3 deletions
|
@ -89,14 +89,11 @@ pop3resp(Pop *pop)
|
|||
char *s;
|
||||
char *p;
|
||||
|
||||
alarm(60*1000);
|
||||
if((s = Brdstr(&pop->bin, '\n', 0)) == nil){
|
||||
close(pop->fd);
|
||||
pop->fd = -1;
|
||||
alarm(0);
|
||||
return "unexpected eof";
|
||||
}
|
||||
alarm(0);
|
||||
|
||||
p = s + strlen(s) - 1;
|
||||
while(p >= s && (*p == '\r' || *p == '\n'))
|
||||
|
|
Loading…
Reference in a new issue