View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004029 | GNUnet | core service | public | 2015-10-27 14:04 | 2015-10-27 14:14 |
| Reporter | Sree Harsha Totakura | Assigned To | Christian Grothoff | Due Date | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | Git master | ||||
| Target Version | 0.11.0pre66 | Fixed in Version | 0.11.0pre66 | ||
| Summary | 0004029: Should CORE be started by default | ||||
| Description | As an after thought of 0003993, I think we should just set CORE to be started automatically by default. This could be achieved by setting `AUTOSTART = YES` in `core.conf.in'. This change makes AUTOSTART to be enabled even if the configure flag `--disable-autostart' is selected. Is this a good change to make? | ||||
| Tags | No tags attached. | ||||
| --disable-autostart is really only an option for highly specialized situations, so I don't think that matters (and would not have fixed/avoided 0003993 either). And the testbed issue arose because of a manual override of the FORCESTART option for all services (which disabled FORCESTART for CADET, which otherwise would have AUTOSTARTED CORE), so that issue would still exist even with this change. So no, I don't think we ought to change this. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-10-27 14:04 | Sree Harsha Totakura | New Issue | |
| 2015-10-27 14:14 | Christian Grothoff | Note Added: 0009809 | |
| 2015-10-27 14:14 | Christian Grothoff | Status | new => closed |
| 2015-10-27 14:14 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2015-10-27 14:14 | Christian Grothoff | Resolution | open => no change required |
| 2015-10-27 14:14 | Christian Grothoff | Fixed in Version | => 0.11.0pre66 |
| 2015-10-27 14:14 | Christian Grothoff | Target Version | => 0.11.0pre66 |