This message was deleted.

Without going into the full agent-based deployment, my first thought would be to nohup this, redirect output to a log file, and throw it in the background, e.g.:

$ nohup ./bin/start-druid > /tmp/logfile 2>&1 &

I just tried it on my Mac install and it seems to work fine.

@John Kowtko Just tried that in AWS EC2 linux machine and when I close the terminal, the service stopped.

Thanks for the reply, it does work although I eventually figured out how to create a file for systemd.

[Unit]
Description=Druid Daemon
Documentation=<http://druid.io|http://druid.io>
Requires=network.target
After=network.target

[Service]
Type=simple
WorkingDirectory=/home/sgautam/Druid/apache-druid-26.0.0
User=sgautam
Group=sgautam
ExecStart=/home/sgautam/Druid/apache-druid-26.0.0/bin/start-druid

[Install]
WantedBy=default.target

Save this as druid.service in /etc/systemd/system/ and then do,

sudo systemctl daemon-reload
sudo systemctl start druid

Hmmm ... you are right, the process stayed active when I "logged out", but was killed when I closed the terminal window ... the default shells work a little differently on a Mac than an old Unix box then ...