MT#55283 fork to background before init HTTP/WS

HTTP/WS init creates worker threads, which would be terminated by a fork
to background. Reverse the order.

Closes #1896
Possibly also relevant to #1895

Change-Id: I30b61e07ad3bed41b6b241e8943ed479277c1474
(cherry picked from commit dd04af1163)
(cherry picked from commit 0bb1cdb403)

daemon/main.c

@@ -1215,12 +1215,12 @@ no_kernel:
 			die("Number of CPU cores is unknown, cannot auto-set socket CPU affinity");
 	}
 
-	if (websocket_init())
-		die("Failed to init websocket listener");
-
 	daemonize();
 	wpidfile();
 
+	if (websocket_init())
+		die("Failed to init websocket listener");
+
 	homer_sender_init(&rtpe_config.homer_ep, rtpe_config.homer_protocol, rtpe_config.homer_id);
 
 	rtcp_init(); // must come after Homer init