On 12/22/09 19:01, Warren Baird wrote: > One thing, though - I thought I saw discussions on the irc a while back > that opkg already is grabbing the CPU resource, so prefixing it with > fsoraw doesn't help --- the issue is that on large upgrades, fsodeviced > gets restarted, and then the hold on the CPU resource is lost...
Ohh, that would be news to me. It would make sense, but actually I doubt it happens already. Yes, fsodeviced being restarted is a killer. Actually I think this will even reset the large timeouts as they are not yet persistent either... (unless you modified frameworkd.conf). > Unfortunately I'm not sure that there are options other than tapping the > screen periodically - or cranking the timeout way up... Nope, unfortunately I don't know of any solution either. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
