[opensuse-buildservice] view=solvstate
Hi! I'm maintaining a build system where one OBS is remote linking against the other. Lately the source server of the latter has been in trouble responding the frequent requests for the binary lists of the repositories. I found that adding: our $usesolvstate = 1; in BSConfig.pm (in the OBS that is remote linking) made the situation better. The difference seems to be that by default the system uses "view=cache" option for the query and now "view=solvstate". For me it seems that with "view=solvstate" the binary list is returned in binary stream directly from :full.solv -file and with "view=cache" the list is parsed in a temporary text file for _each request_ and that is taking a long time. I'd just like to know why "view=cache" is the default and if there are some drawbacks when using "view=solvstate"? And how the hell the api.opensuse.org can handle the situation? :) -Johannes -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Nov 08, 2011 at 11:41:49AM +0200, Johannes Lahti wrote:
I'd just like to know why "view=cache" is the default and if there are some drawbacks when using "view=solvstate"?
Sat-solver's solv parser was never checked against corrupt solv files, so it's probably possible to exploit it and do nasty things. That's not a problem for libzypp, as it only handles solv files written by itself. So I didn't dare to make view=solvstate the default because of security reasons. If you trust the other side, you can use it to speed up things.
And how the hell the api.opensuse.org can handle the situation? :)
I don't know, it doesn't seem to be an issue here. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ok. Thank you for the clear up!
And how the hell the api.opensuse.org can handle the situation? :)
I don't know, it doesn't seem to be an issue here.
Nice to hear that. :) You definitely have more horsepower in use, but I can imagine that the number of requests is huge. -Johannes -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Nov 08, 2011 at 11:41:49AM +0200, Johannes Lahti wrote:
I'd just like to know why "view=cache" is the default and if there are some drawbacks when using "view=solvstate"?
Sat-solver's solv parser was never checked against corrupt solv files, so it's probably possible to exploit it and do nasty things. That's not a problem for libzypp, as it only handles solv files written by itself. So I didn't dare to make view=solvstate the default because of security reasons. If you trust the other side, you can use it to speed up things.
And how the hell the api.opensuse.org can handle the situation? :)
I don't know, it doesn't seem to be an issue here. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ok. Thank you for the clear up!
And how the hell the api.opensuse.org can handle the situation? :)
I don't know, it doesn't seem to be an issue here.
Nice to hear that. :) You definitely have more horsepower in use, but I can imagine that the number of requests is huge. -Johannes -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Johannes Lahti -
Michael Schroeder