-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tt
should be able to work without daemonization
#869
Comments
psergee
added a commit
that referenced
this issue
Jul 12, 2024
Use standard go logging instead of lamberjack. Part of #869
psergee
added a commit
that referenced
this issue
Jul 12, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 12, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 29, 2024
Use standard go logging instead of lamberjack. Part of #869
psergee
added a commit
that referenced
this issue
Jul 29, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 29, 2024
Use standard go logging instead of lamberjack. Part of #869
psergee
added a commit
that referenced
this issue
Jul 29, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 30, 2024
Use standard go logging instead of lamberjack. Part of #869
psergee
added a commit
that referenced
this issue
Jul 30, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 30, 2024
Use standard go logging instead of lamberjack. Part of #869
psergee
added a commit
that referenced
this issue
Jul 30, 2024
Closes #869 @TarantoolBot document Title: `tt start` interactive mode This patch adds support for `tt start` interactive mode with `-i/--interactive` flag. In this mode `tt` will wait for child Tarantool process completions. Standard output will be used instead of the default log files. Use Ctrl-C combination to stop `tt` and its child Tarantool instances. No watchdog processes created.
psergee
added a commit
that referenced
this issue
Jul 30, 2024
Use standard go logging instead of lamberjack. Part of #869
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
tt start
only works in daemon mode. This makes its usage in Docker very tricky, as the roottt start
process exits after the child processes start. Perhaps it would be more convenient to start instances and wait for them by default, and enable daemonization only when the-d
option is specified.Additionally, in non-daemon mode, the
tt start
command should by default print its child output to the standard output (stdout), not to log files. It should also be possible to enable the standard output in daemon mode, as it can be useful whentt start
is used with systemd, as all output will go to the system journal and can be viewed using thejournalctl
command.After making these changes,
tt start
can be easier to use in a Docker container and with systemd.The text was updated successfully, but these errors were encountered: