From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id EBA071381FA for ; Mon, 12 May 2014 17:02:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 729E5E0B8A; Mon, 12 May 2014 17:02:12 +0000 (UTC) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 39BD3E0B0C for ; Mon, 12 May 2014 17:02:11 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id e16so2147723lan.14 for ; Mon, 12 May 2014 10:02:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=flD+tUaLAOD+mbvy7TqxOHT/1sZmrHtoDoTCa5RMouY=; b=TZvROY3ws7pgX12VlvkKhl35Xf0698RRKSVqOAziOt9O0h4/D5qt0hQrpHTkcXGWsr V/Kkns3aWRpNycPguPMMgcQCHQDMaVgj1eKbiWSxlqSFzRBpqsV/P5Bb5//qj21uUsws 1WcoImTAjvFG9EFn7D64nT8Rnkdw0yO19VzsTlBiDbN79KtKPzpAV6zEi/xEH4YiJa89 jkv43FpJj0mvR+sb/AGYoN/DB/Cw+J6mlcDyt2lV4+/5COYQ9kolWG4d3HjZPPidBPzj jctU6elMaXO+Xz2lnFDRodWvNvdLpMCuFSa1R1y8AHjPoXzP77YauObcxd8BxECs2P2V R+Yw== X-Received: by 10.112.131.8 with SMTP id oi8mr356581lbb.87.1399914129615; Mon, 12 May 2014 10:02:09 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.114.170.166 with HTTP; Mon, 12 May 2014 10:01:49 -0700 (PDT) In-Reply-To: <17066.1399913526@ccs.covici.com> References: <23736.1399879340@ccs.covici.com> <17435.1399889735@ccs.covici.com> <13680.1399912266@ccs.covici.com> <17066.1399913526@ccs.covici.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Mon, 12 May 2014 12:01:49 -0500 Message-ID: Subject: Re: [gentoo-user] problems getting systemd to work To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7fc9f2b0-cfc0-428b-8f5c-0676e11ddc1d X-Archives-Hash: bb2f8e7272981ba103e616591aaba1d2 On Mon, May 12, 2014 at 11:52 AM, wrote: > Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> On Mon, May 12, 2014 at 11:31 AM, wrote: >> [snip] >> > OK, I will try dracut, >> >> I hope it works with dracut. This is my kernel command line and >> RAID/LVM related stuff from GRUB2: >> >> GRUB_CMDLINE_LINUX=3D"init=3D/usr/lib/systemd/systemd quiet nosplash" >> GRUB_PRELOAD_MODULES=3D"lvm mdraid1x" >> >> And this is my dracut.conf (minus comments): >> >> add_dracutmodules+=3D"crypt lvm mdraid systemd" >> add_drivers+=3D"autofs4 ipv6 dm-crypt aes sha256" >> fscks=3D"umount mount /sbin/fsck* e2fsck" >> >> That's it. I didn't touched anything else to make dracut+systemd work >> with LVM and RAID (and LUKS, but that doesn't matter). >> >> Also, dracut comes with extensive and very clear documentation; check >> the man pages included. >> >> > but I still want to know what systemd is doing, >> > what processes its spawning, etc. -- how can I find this out -- I >> > thought to use the confirm_spawn, but it times out and keeps going, wh= at >> > can I do instead? >> >> You can use bootchart: >> >> man 1 systemd-bootchart >> >> It will produce a chart with all the processes, and how long it takes >> for every one of them. But remember, the order depends on which one >> finishes before, and that can change from boot to boot. >> >> > Thanks people for all your responses, this is a great list. >> >> Regards. >> -- >> Canek Pel=C3=A1ez Vald=C3=A9s >> Profesor de asignatura, Facultad de Ciencias > > Well, since I am unable to see, the graph would not do me any good, any > way to get it in text form? What I want to see (and I know the order > may change) is which starts first and so on, to make sure targets, > etc. do what I want them to do. Try adding this to your kernel command line: systemd.log_target=3Dconsole systemd.log_level=3Ddebug. It will add a lot of output, including what is being executed. Everything is documented in the man page: man 1 systemd. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico