Hi Chris Very happy to receive a reply, I think giving an error message is a good solution.
> 2024年8月28日 18:15，Christofer Dutz <christofer.d...@c-ware.de> 写道： > > Hi, > > It reports a non-0 exit code if you don’t provide any option. In this > particular case it returns 1. > > The test for it is here: > https://github.com/apache/iotdb/blob/master/iotdb-core/node-commons/src/test/java/org/apache/iotdb/commons/ServerCommandLineTest.java#L37 > > It also seems that there was a difference between the ConfigNode startup > (which seems to have allowed a default startup) and the DataNode (which would > print the usage and fail) > Streamlining this to match is in my opinion the best way to do it. And I > think not using a default is the best option. > > But we’re an open-source project … happy to change that if the community > decides to (but then to ensure all types of nodes handle it equally) > > Chris > > > Von: yu yong <1471335...@qq.com.INVALID> > Datum: Mittwoch, 28. August 2024 um 10:17 > An: dev@iotdb.apache.org <dev@iotdb.apache.org> > Betreff: ConfigNode does not have a default startup mode > Hi all, > > Just now I failed to start ConfigNode after pulling the latest commit from > the master branch. > > And I found out that the default startup mode -s or -r was not added after > 38c1d5 > <https://github.com/apache/iotdb/commit/38c1d591acfabdae4bbf542100090652416d2027> > commit, and it didn't report an error. > > So I suggest to add the default startup mode or throw an exception if the > user didn't specify the default startup mode.
