On Thu, Aug 15, 2013 at 03:42:27PM +0800, WANG Chao wrote:
Now kdump.service runs "After" network.target. But
network.target
doesn't mean network is setup and online[1]. 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).
1.
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
I think this dependency might create some issues. What if kdump.conf is
not dumping to an nfs/ssh target. What if there is a configuration issue
and a network interface is not coming up. Does that mean kdump service
will not run at all in that case?
Thanks
Vivek
---
I tested local/nfs/ssh dump. Local and nfs dump works ok. But ssh dump has a
problem (not related to kdump).
I opend a bz to NetworkManager:
https://bugzilla.redhat.com/show_bug.cgi?id=997318
kdump.service | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kdump.service b/kdump.service
index 07e97fa..55b7ca2 100644
--- a/kdump.service
+++ b/kdump.service
@@ -1,6 +1,6 @@
[Unit]
Description=Crash recovery kernel arming
-After=network.target
+After=network.target network-online.target remote-fs.target
[Service]
Type=oneshot
--
1.8.3.1
_______________________________________________
kexec mailing list
kexec(a)lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/kexec