On Mon, 2004-08-09 at 09:01, seth vidal wrote: > On Mon, 2004-08-09 at 08:51 -0400, David L. Parsley wrote: > > I had a user report which I've now duplicated: the yum nightly cronjob > > hung. netstat -t -p revealed it still had an ESTABLISHED connection to > > a repo, and strace -p (yum process) showed it sitting and waiting in a > > read(6, ...), where 6 is a socket; I'm guessing it was trying to read > > something from the repository, but just not getting anything. Is it > > possible there's a transfer that's not timing out? > > > > Yes or they could have set retries to 0 and it's infinitely retrying. Ok, retries isn't set, so defaulting to 6; this is yum 2.0.7, btw. Should there be a client timeout on transfers? regards, David > > -sv > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20040809/05a3965d/attachment.bin
