From 163f84805eaf548020b88d65586979650c6a4795 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 23 Sep 2015 13:01:39 -0400 Subject: comment --- ...omment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment new file mode 100644 index 00000000..eb951ca6 --- /dev/null +++ b/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2015-09-23T16:52:12Z" + content=""" +Ah, that makes much more sense; rather than a strange ssh problem, +propellor is apparently exiting 0 w/o doing anything when run +with `./propellor --continue 'SimpleRun "xxx"'` or something close to that. + +So, this might have to do with the old propellor not supporting SimpleRun, +which was added back in 0.4.0. + +Or, more likely, it's broken in some way that makes it not do anything when +asked to so a SimpleRun for a particular host. + +You can probably try running the old propellor with that SimpleRun parameter and +the command line and get a better feel for what it's doing, and if desired, +bisect or otherwise instrument the program to see why it behaved this way. +"""]] -- cgit v1.3-2-g0d8e