Common problem sequence:

1. Run steampipe service start
2. Do other fun things, e.g. play basketball, forgetting about 1
3. Run steampipe query (which silently connects to the service started in 1)
4. Get confused why things seem configured differently from what you expected in 3 (since you thought it would start then)

We need to make this easier!

Proposal: Print information at startup about whether Steampipe started it's own (temporary) service or if it connected to an existing one. I'm not sure if that should be printed either way all the time, or just print a warning when you connect to an existing steampipe service. (I think the latter.)