[GH-ISSUE #4017] log.to = "./frps.log" 为何为保存在在根目录？而不是相对目录呢？

gitea-mirror commented

2026-05-05 14:03:23 -06:00

Owner

Copy link

Originally created by @fsleo on GitHub (Feb 21, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4017

Bug Description

[apps:/]$ ls
bin boot data dev etc frps.log

frpc Version

0.54.0

frps Version

0.54.0

System Architecture

linux/aarch64

Configurations

...

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @fsleo on GitHub (Feb 21, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4017 ### Bug Description [apps:/]$ ls bin boot data dev etc frps.log ### frpc Version 0.54.0 ### frps Version 0.54.0 ### System Architecture linux/aarch64 ### Configurations ... ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:03:23 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:03:27 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (Feb 27, 2024):

工作路径

@xqzr commented on GitHub (Feb 27, 2024): 工作路径

gitea-mirror commented

2026-05-05 14:03:28 -06:00

Author

Owner

Copy link

@fsleo commented on GitHub (Mar 6, 2024):

工作路径

可是我的程序在 /usr/local/frp/frps.exe

@fsleo commented on GitHub (Mar 6, 2024): > 工作路径可是我的程序在 /usr/local/frp/frps.exe

gitea-mirror commented

2026-05-05 14:03:29 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 29, 2024):

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

@github-actions[bot] commented on GitHub (Mar 29, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:03:30 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 20, 2024):

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

@github-actions[bot] commented on GitHub (Apr 20, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified