Henne, my man ;-) On Thursday, July 25, 2013 10:24:31 AM Hendrik Vogelsang wrote: > On 24.07.2013 12:23, Stefan Botter wrote: : > > I am not really sure, how the contraints management in OBS is > > working (regarding the workers). As usual the documentation is > > sparse at best. I do not know how the dispatcher gets to know of > > the capabilities of workers, and if this is a feature in newer > > versions of the workers only. > > The hardware get's analyzed every time a build is run (see > $workerenvstate in bs_worker) and with the _constraints file you can > match against that. > > > My workers "should" provide the necessary resources, at least > > swkj04 and swkj07, the workers run in chroot mode and have thus, > > at least potentially, access to the whole system resources, as > > long as the other processed do not fill up their (RAM)disks to the > > max. > > In the same function you'll find the explanation. memory is undefined > in non vm mode since no guarantees exist :-)
So having the _contraints in an all-chroot env is worthless, or better "buildless" ;-) > > In the past - before the crash and before I added my workers, there > > were at least three more workers provided by [not me], which are > > now "lost in time and space" - meaning, I do not know who ran them > > and how to contact them. These machines obviously had no problem > > compiling resource-hungry packages. > > You should have all the access info in the backup, AFAIR it involved > also an openvpn setup somehow... Hm. No. The workers have the openVPN definition with the server address (IP, not name). On the server I only have a bunch of keys, no names, addresses :( OK, in the logs I see the IP addresses, but that is worthless also. > Henne Stefan -- Stefan Botter zu Hause Bremen
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Packman mailing list [email protected] http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
