kk worked, thanks 🙂
Since it's just a board to test NodeBB it's ok to reset anything 🙂
as I'm always on master-branch, I noticed a new "feature":
if I start nodebb via
./nodebb dev and send kill signal it shuts down and starts again like
info: NodeBB Ready ^Cinfo: [app] Shutdown (SIGTERM/SIGINT) Initialised. info: [app] Database connection closed. info: [app] Shutdown complete. info: NodeBB v0.4.1 Copyright (C) 2013 DesignCreatePlay Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Fri Apr 18 2014 02:40:41 GMT+0200 (CEST) info: Initializing NodeBB v0.4.1 [...] info: NodeBB Ready
So I currently have to kill it multiple times until I get the life-saving message
[loader] Experienced three start attempts in 10 seconds, most likely am error on startup. Halting.
It's a bit annoying
Does anybody else notice this?
From a previous topic, that's not a bug. It's designed to work like that..
Ok, is there anything I can do against this? Maybe a hard-coded key to shutdown without restart like 'q' would be fine ^^
But looking into loader.js shows me
process.on('SIGINT', nbb_stop); process.on('SIGTERM', nbb_stop); process.on('SIGHUP', nbb_restart);
and a test approves that nbb_stop gets called, not nbb_restart so it doesn't seem to be intended to me.
Ping the devs. They are in a better position to tell you how to get around the feature.
@frissdiegurke Fixed as of 7aa785b (22:36 EDT)