sshkit 0.0.8 → 0.0.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,6 +3,10 @@
3
3
  This file is written in reverse chronological order, newer releases will
4
4
  appear at the top.
5
5
 
6
+ ## 0.0.9
7
+
8
+ * Include more attributes in `Command#to_hash`.
9
+
6
10
  ## 0.0.8
7
11
 
8
12
  * Added DSL method `background()` this sends a task to the background using
data/FAQ.md CHANGED
@@ -15,3 +15,32 @@ deployments.
15
15
 
16
16
  It's in private Beta use, and the documentation could use more work, but this
17
17
  is open source, that's more or less how it works.
18
+
19
+ ## Why does <something> stop responding after I started it with `background()`?
20
+
21
+ The answer is complicated, but it can be summed up by saying that under
22
+ certain circumstances processes can find themselves connected to file
23
+ descriptors which no longer exist.
24
+
25
+ The following resources are worth a read to better understand what a process
26
+ must do in order to daemonize reliably, not all processes perform all of the
27
+ steps necassary:
28
+
29
+ * [http://stackoverflow.com/questions/881388/what-is-the-reason-for-performing-a-double-fork-when-creating-a-daemon]
30
+
31
+ This can be summarized as:
32
+
33
+ > On some flavors of Unix, you are forced to do a double-fork on startup, in order to go into daemon mode. This is because single forking isn’t guaranteed to detach from the controlling terminal.
34
+
35
+ If you experience consistent problems, please report it as an issue, I'll be
36
+ in a position to give a better answer once I can examine the problem in more
37
+ detail.
38
+
39
+ ## My daemon doesn't work properly when run from SSHKit
40
+
41
+ You should probably read:
42
+
43
+ * http://www.enderunix.org/docs/eng/daemon.php
44
+
45
+ If any of those things aren't being done by your daemon, then you ought to
46
+ adopt some or all of those techniques.
@@ -102,7 +102,14 @@ module SSHKit
102
102
  options: options,
103
103
  exit_status: exit_status,
104
104
  stdout: stdout,
105
- stderr: stderr
105
+ stderr: stderr,
106
+ started_at: @started_at,
107
+ finished_at: @finished_at,
108
+ uuid: uuid,
109
+ started: started?,
110
+ finished: finished?,
111
+ successful: successful?,
112
+ failed: failed?
106
113
  }
107
114
  end
108
115
 
@@ -1,3 +1,3 @@
1
1
  module SSHKit
2
- VERSION = "0.0.8"
2
+ VERSION = "0.0.9"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: sshkit
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.8
4
+ version: 0.0.9
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -10,7 +10,7 @@ authors:
10
10
  autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
- date: 2013-01-17 00:00:00.000000000 Z
13
+ date: 2013-01-18 00:00:00.000000000 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: net-ssh