On Mon, Nov 12, 2012 at 3:40 PM, Keith Dart <ke...@dartworks.biz> wrote: > Re > 20121111192731.149dc082@dartworks.biz20121111192731.149dc082@dartworks.bizCADPrc83TGeegA0UXadMEy=B62xZYOE50bqfw+dxDJ8f=FkPTHA@mail.gmail.com20121111185801.58964939@dartworks.bizCADPrc83+5zUQ+GzCSvyHhZa7BZfMqqagZCosktasOY1sdhCx0Q@mail.gmail.com20121111175313.54b9acf1@dartworks.bizCADPrc80EwExpbdcJX1a+aE0DA=iopqw-QOaozmUBJCs5FGew-g@mail.gmail.com20121109171149.1d8a3e18@dartworks.biz509D9C62.9040909@gmail.com509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, > Canek Peláez Valdés said: >> That it's weird. What does "systemd-analyze blame" say after a fresh >> boot? > > > Something related to consolekit was taking by far the most time. But I > thought I was supposed to remove that. So I make USE include > -consolekit, and removed console kit, and did "emerge -uD --newuse > world", but yet, pambase insists on pulling in consolekit no matter > what. I compile it separate (emerge -1 ...) without consolekit USE, and > the works. But whenever I update consolekit wants get added again.
Do an "equery depends pambase" and see what it's trying to pull pambase with consolekit. Perhaps do you have something in /etc/portage/package.use? > Anyway, right now I have it removed and it does come up faster without > it. Cool. > But another thing I miss is knowing where it is in the boot process. > The systemd doesn't tell me anything. Actually it does; if you are not using plymouth (or another splash), the standard listing of services gets printed on the console, with even the "[ OK ]" that a lot of people like. A copy of this output gets logged in /var/log/boot.log. Also, you can boot with systemd.log_target=kmsg systemd.log_level=debug, and everything (which is a lot) will get stored in the kernel ring buffer, so you can check it out afterwards with dmesg. The thing with this output is that, when properly configured, systemd is just too fast for it to be useful; my laptop boots so fast that I cannot even see it even if I disable plymouth. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
