Re: cups - debuild - pbuilder
Antonio Terceiro <[email protected]>
| Newsgroups | gmane.linux.debian.devel.portuguese |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 06, 2014 at 02:40:49PM -0200, Herbert Parentes Fortes Neto wrote: > ok, feito. > > o lpstat é executado. a resposta é "scheduler is not running". mas antes > é informado o pid do scheduler. > > teria que aparecer em '/var/cache/pbuilder/build/proc' ? > > abaixo a saída do 'pbuilder build': > > Starting scheduler: > ../scheduler/cupsd -c /tmp/cups-root/cupsd.conf -f > >/tmp/cups-root/log/debug_log 2>&1 & > > Scheduler is PID 24161. > > ---------------- > ../systemv > ../systemv/cupsctl.o > ../systemv/lpstat.c > ../systemv/accept > ../systemv/cupsaccept > ../systemv/cupsaddsmb > ../systemv/lp.c > ../systemv/Dependencies > ../systemv/cupsaddsmb.o > ../systemv/lp > ../systemv/lpoptions > ../systemv/lp.o > ../systemv/lpoptions.o > ../systemv/cupstestppd.o > ../systemv/cupsctl.c > ../systemv/lpinfo.c > ../systemv/cancel > ../systemv/lpmove.o > ../systemv/cupsdisable > ../systemv/lpadmin.o > ../systemv/cupsctl > ../systemv/cupsaccept.c > ../systemv/cupstestppd.c > ../systemv/lpadmin > ../systemv/cupsenable > ../systemv/cupstestdsc > ../systemv/cupstestdsc.o > ../systemv/cancel.o > ../systemv/cupsreject > ../systemv/lppasswd > ../systemv/reject > ../systemv/cancel.c > ../systemv/lppasswd.o > ../systemv/cupstestppd > ../systemv/Makefile > ../systemv/lpoptions.c > ../systemv/cupstestdsc.c > ../systemv/lpmove.c > ../systemv/cupsaccept.o > ../systemv/lpstat.o > ../systemv/lpmove > ../systemv/lpinfo > ../systemv/lpstat > ../systemv/lpinfo.o > ../systemv/cupsaddsmb.c > ../systemv/lppasswd.c > ../systemv/lpadmin.c > ---------------- > > scheduler is not running > Waiting for scheduler to become ready... > scheduler is not running > Waiting for scheduler to become ready... meu palpite é de que esse troço depende de algum detalhe do sistema que é diferente entre o sbuild (ferramenta "moderna" de build em chroot, usado pelos buildds oficiais) e o pbuilder; pra investigar isso você vai ter que olhar o código do lpstat, parece, pra ver como ele testa se esse scheduler está rodando ou não, e tentar entender o que é que tem no sbuild que não tem no pbuilder (ou vice-versa). -- Antonio Terceiro <[email protected]>
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUW7JYAAoJEPwNsbvNRgveDHoP/3OhnwvFoDgc+U/RLsr8ebVX ku+mjGve2x2sbbDg3caWGDyjHbiUSzxmqH0Q/1yLzN2TR5ZzmSbitzUsBv/pSaqw GtW90tUrS+neVrjTljty1H53zWtPYf0li7Voa0l67uron0RdJyQs461ge0M7STKu EtiQbugZcxLquU9H9lDc4KbXrZ7huTiOVTDoUae6hYmCsUKaXT64J6ab2EJzpP+g nf0s8Oc24VAEbAAJxWykgSHTMPakjwgh9dwx/D3afOOtAGuaEY9+ROarkIEndteg tchTQmS6u3VDVzPBMGcTkLflXf/pvGIs6ju048yKJ0T2EBWoDNh2LFvy6rpA4gcp s3meC1S5ZEOxKOxeV38dQ4ruTZXgumyO7uw84H/NZgoMr7O88aYglW6eXzXUIC/q scIDRkCuKI3naPIY9Predhh9coexViTrs9LBBVCPsY+pFEZvMP6L6p1yjp7HPo/f Xw3IhXK7tEEvjARD+zXBl734TAjS5frm97VZjI9ky2OQQi3RJGbjK2QkYWUCKqtz l4ecubPrXCJ+NtjwlYBjmJgEJusWJr68Uq2dmG5+Bi/XTXd0OFvYdyrvtM2jzi6R jlOUvKRySOsxb9Siq44+MqPiELH6O8FEYv8Hh4iu+WMFAHiN4QV3NXzGMhF1ZzHT x6uLTVJ3E7GkfVEf2Qrw =VqAF -----END PGP SIGNATURE-----