Commit b5d2186
committed
Fix: unable to restart container after it was killed
When the process name found by the PID file and the PID in the PID file
are the same it should be treated as it is from another process so that
ospd-openvas can be started even after a sudden kill of a container.
To verify this change you can start ospd-openvasby executing:
```
docker run -v /run/redis/redis.sock:/run/redis/redis.sock \
--name "narf" \
--privileged greenbone/ospd-openvas:unstable ospd-openvas -f
```
Then kill it via:
```
docker kill narf
```
and restart it with
```
docker start -a narf
```
Fixes: #7251 parent a6a017b commit b5d2186
1 file changed
+12
-11
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
103 | 103 | | |
104 | 104 | | |
105 | 105 | | |
106 | | - | |
107 | | - | |
| 106 | + | |
| 107 | + | |
108 | 108 | | |
109 | 109 | | |
| 110 | + | |
| 111 | + | |
110 | 112 | | |
111 | 113 | | |
112 | | - | |
113 | | - | |
114 | | - | |
| 114 | + | |
| 115 | + | |
115 | 116 | | |
116 | | - | |
117 | | - | |
| 117 | + | |
| 118 | + | |
118 | 119 | | |
119 | 120 | | |
120 | 121 | | |
121 | | - | |
| 122 | + | |
122 | 123 | | |
123 | 124 | | |
124 | 125 | | |
| |||
130 | 131 | | |
131 | 132 | | |
132 | 133 | | |
133 | | - | |
134 | | - | |
135 | | - | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
136 | 137 | | |
137 | 138 | | |
138 | 139 | | |
| |||
0 commit comments