-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/03/2013 09:01 PM, Andrei B wrote: > Well, that would be an idea. However, multipathd has the pidfile > hardcoded. It cannot be changed at runtime, nor can it be > disabled. It's not pretty but if you really want the daemon running this early (most distros without /run don't bother) you can modify the init script to mount some writable (e.g. ramfs/tmpfs) location over the top of the read-only /var during start up. E.g.: mount -t ramfs none /var/run/ > I know, I could compile it with a different hardcoded path, but > that's really a bad idea, because then if multipathd were to be > restarted anytime later after boot, it would then fail because of > the same reason. Since the daemon only manages path monitoring and failback when paths are down most distros that need to cope with read only /var (i.e. pre-systemd and /run) do not start multipathd until later in the boot process when /var has been made writable. Regards, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlE0fDYACgkQ6YSQoMYUY97ZEgCgsgdZfaVC8D1ZCfhY93UPA9Sh BEEAniaeRZTap/rbp6pbanE78DpD3myy =ZTTO -----END PGP SIGNATURE----- -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
