github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 16:15:49 -06:00

[GH-ISSUE #2224] 能不能增加控制台显示并存储日志功能 #1767

New issue

Closed

opened 2026-05-05 13:08:20 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 13:08:20 -06:00

Owner

Originally created by @AC-027 on GitHub (Jan 28, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2224

能不能增加控制台显示并同时存储日志功能。
目前好像只能是控制台显示或者配置路径保存文件二选一。

Originally created by @AC-027 on GitHub (Jan 28, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2224 能不能增加控制台显示并同时存储日志功能。目前好像只能是控制台显示或者配置路径保存文件二选一。

gitea-mirror

2026-05-05 13:08:20 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:08:23 -06:00

Author

Owner

@darylchen97 commented on GitHub (Jan 30, 2021):

你可以写入文件，并且用tail读取文件

@darylchen97 commented on GitHub (Jan 30, 2021): 你可以写入文件，并且用tail读取文件

gitea-mirror commented

2026-05-05 13:08:24 -06:00

Author

Owner

@wangrui027 commented on GitHub (Feb 2, 2021):

nohup ./frps -c ./frps.ini > ./frps.log &

后台运行并输出日志到frps.log，自己替换路径

@wangrui027 commented on GitHub (Feb 2, 2021): ``` bash nohup ./frps -c ./frps.ini > ./frps.log & ``` 后台运行并输出日志到`frps.log`，自己替换路径

gitea-mirror commented

2026-05-05 13:08:25 -06:00

Author

Owner

@wangrui027 commented on GitHub (Feb 2, 2021):

然后tail -f你的日志文件

@wangrui027 commented on GitHub (Feb 2, 2021): 然后`tail -f`你的日志文件

gitea-mirror commented

2026-05-05 13:08:26 -06:00

Author

Owner

@AC-027 commented on GitHub (Feb 2, 2021):

非常感谢您的回复。
可是我是在WINDOWS平台下用，并没有能执行。

@AC-027 commented on GitHub (Feb 2, 2021): 非常感谢您的回复。可是我是在WINDOWS平台下用，并没有能执行。

gitea-mirror commented

2026-05-05 13:08:26 -06:00

Author

Owner

@darylchen97 commented on GitHub (Feb 2, 2021):

windows下可以不适用nohup

@darylchen97 commented on GitHub (Feb 2, 2021): windows下可以不适用nohup

gitea-mirror commented

2026-05-05 13:08:27 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 20, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Mar 20, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.