Well, that would be an idea. However, multipathd has the pidfile hardcoded. It cannot be changed at runtime, nor can it be disabled. 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. On 2013-03-03 01:42 PM, Gabriel de Perthuis wrote: >> The problem is that multipathd wants to create a PID file under /var >> (which is at this time readonly). This fails and multipathd fails to >> start. > Distros handle this by putting pidfiles in /run, a tmpfs set up at early > boot. There might be some magic to ensure that later mounts don't shadow > it. > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
