I don't see any fundamental issue with providing a NET_WAIT_TIME variable (probably should be namespaced to KDUMP_) in the kdump config file, but:
1) this seems like a hack to work around slow hardware, right? 2) it can't be automatically deduced, afaict. Or do you want to have 30s delays (potentially) on all POWER machines? 3) I'm not 100% familiar with the 'upstream' of kdump-tools -- is this something that we'd need to carry forever in the Debian/Ubuntu packaging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
