On Wed, Sep 25, 2013 at 08:35:05PM +0800, WANG Chao wrote:
Now kdump.service runs "After" network.target. But
doesn't mean network is setup and online. We should use
network-online.target instead for ssh/nfs dump.
And also because nfs dump requires a mounted nfs when rebuilding kdump
initrd, kdump.service should also run "After" remote-fs.target (this
means all remote fs configured in /etc/fstab is mounted).
The downside of this patch is we always need to wait for network-online.target
even when dump target is a local disk. If network fails to come up,
kdump.service have to be stuck until network-online.target timeout (90
seconds by default).
This will most likely be a problem down the line and we will have to fix
it as discussed in other mail and change kdump.service link on the fly
based on whether dump target is local or requires network.
Anyway, for the time being, let us take this patch in and see how well
does it work.
Acked-by: Vivek Goyal <vgoyal(a)redhat.com>
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
kdump.service | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kdump.service b/kdump.service
index 07e97fa..55b7ca2 100644
@@ -1,6 +1,6 @@
Description=Crash recovery kernel arming
+After=network.target network-online.target remote-fs.target