| 1 |
On Wed, May 14, 2014 at 4:43 AM, <covici@××××××××××.com> wrote: |
| 2 |
> Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> On Mon, May 12, 2014 at 11:52 AM, <covici@××××××××××.com> wrote: |
| 5 |
>> > Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 6 |
>> > |
| 7 |
>> >> On Mon, May 12, 2014 at 11:31 AM, <covici@××××××××××.com> wrote: |
| 8 |
>> >> [snip] |
| 9 |
>> >> > OK, I will try dracut, |
| 10 |
>> >> |
| 11 |
>> >> I hope it works with dracut. This is my kernel command line and |
| 12 |
>> >> RAID/LVM related stuff from GRUB2: |
| 13 |
>> >> |
| 14 |
>> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash" |
| 15 |
>> >> GRUB_PRELOAD_MODULES="lvm mdraid1x" |
| 16 |
>> >> |
| 17 |
>> >> And this is my dracut.conf (minus comments): |
| 18 |
>> >> |
| 19 |
>> >> add_dracutmodules+="crypt lvm mdraid systemd" |
| 20 |
>> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256" |
| 21 |
>> >> fscks="umount mount /sbin/fsck* e2fsck" |
| 22 |
>> >> |
| 23 |
>> >> That's it. I didn't touched anything else to make dracut+systemd work |
| 24 |
>> >> with LVM and RAID (and LUKS, but that doesn't matter). |
| 25 |
>> >> |
| 26 |
>> >> Also, dracut comes with extensive and very clear documentation; check |
| 27 |
>> >> the man pages included. |
| 28 |
>> >> |
| 29 |
>> >> > but I still want to know what systemd is doing, |
| 30 |
>> >> > what processes its spawning, etc. -- how can I find this out -- I |
| 31 |
>> >> > thought to use the confirm_spawn, but it times out and keeps going, what |
| 32 |
>> >> > can I do instead? |
| 33 |
>> >> |
| 34 |
>> >> You can use bootchart: |
| 35 |
>> >> |
| 36 |
>> >> man 1 systemd-bootchart |
| 37 |
>> >> |
| 38 |
>> >> It will produce a chart with all the processes, and how long it takes |
| 39 |
>> >> for every one of them. But remember, the order depends on which one |
| 40 |
>> >> finishes before, and that can change from boot to boot. |
| 41 |
>> >> |
| 42 |
>> >> > Thanks people for all your responses, this is a great list. |
| 43 |
>> >> |
| 44 |
>> >> Regards. |
| 45 |
>> >> -- |
| 46 |
>> >> Canek Peláez Valdés |
| 47 |
>> >> Profesor de asignatura, Facultad de Ciencias |
| 48 |
>> > |
| 49 |
>> > Well, since I am unable to see, the graph would not do me any good, any |
| 50 |
>> > way to get it in text form? What I want to see (and I know the order |
| 51 |
>> > may change) is which starts first and so on, to make sure targets, |
| 52 |
>> > etc. do what I want them to do. |
| 53 |
>> |
| 54 |
>> Try adding this to your kernel command line: |
| 55 |
>> systemd.log_target=console systemd.log_level=debug. It will add a lot |
| 56 |
>> of output, including what is being executed. |
| 57 |
> |
| 58 |
> I also in my kernel command line said rd.lvm=1 just to make sure. |
| 59 |
|
| 60 |
John, which version of dracut are you using? Also, what was the |
| 61 |
command line you used to generate it? |
| 62 |
|
| 63 |
Regards. |
| 64 |
-- |
| 65 |
Canek Peláez Valdés |
| 66 |
Profesor de asignatura, Facultad de Ciencias |
| 67 |
Universidad Nacional Autónoma de México |
Archives