"--log=" option for server
m-ichael opened this issue · 3 comments
m-ichael commented
log file stays empty, this could be a non-bug, since ssh-chat runs correctly.
using "--log="/home/user/some-writable-file", using "" quotes or without quoting the option second part.
What i would like is to have a chat record that is longel (say 1000 lines), whether this is history is written to a log file, or any other solution.
shazow commented
The log is written to when there is chat activity. Try connecting to the server and checking the log file after that. :) It should get you what you want.
shazow commented
m-ichael commented
My mistake, the --log="path/to/file" was added, but i did not restart the
ssh-chat binary.
Indeed, the log file logs the chat history, any restrictions as to the size
of the log file? Is the log file is persistent, after restart of binary the
log file is appended to, not overwritten when the server is stopped, then
restarted. That is expected behaviour.
To have different conversations, for now: run the same binary on a
different port in parallel, but then a remote user would have the choice as
to which server to connect.
thnks for your fast reply,
…On Wed, 19 Jun 2024 at 16:37, Andrey Petrov ***@***.***> wrote:
The log is written to when there is chat activity. Try connecting to the
server and checking the log file after that. :) It should get you what you
want.
—
Reply to this email directly, view it on GitHub
<#429 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZM4BCTMSNLWVWMZOBRSV3ZIGJTVAVCNFSM6AAAAABJSDJM42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYHA3TIOBWGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>