[GH-ISSUE #4147] The value of log.to cannot be configured as a non-existent path #3271

Closed
opened 2026-05-05 14:06:48 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @FoundAdd on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4147

Describe the feature request

If I configure log.to with a path that does not exist, the logging system will not automatically create this directory, but will directly prompt "no such file or directory".
image

Describe alternatives you've considered

It would be much more convenient if the logic could be changed to automatically create lower-level directories. Currently, the corresponding log directory can only be created in advance.

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @FoundAdd on GitHub (Apr 10, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4147 ### Describe the feature request If I configure log.to with a path that does not exist, the logging system will not automatically create this directory, but will directly prompt "no such file or directory". ![image](https://github.com/fatedier/frp/assets/58539321/d37558d2-4733-41eb-b90f-b78620c2e1c6) ### Describe alternatives you've considered It would be much more convenient if the logic could be changed to automatically create lower-level directories. Currently, the corresponding log directory can only be created in advance. ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others
gitea-mirror 2026-05-05 14:06:48 -06:00
Author
Owner

@fatedier commented on GitHub (Apr 11, 2024):

Please use the latest version and use explicit paths instead of environment variables.

<!-- gh-comment-id:2048841539 --> @fatedier commented on GitHub (Apr 11, 2024): Please use the latest version and use explicit paths instead of environment variables.
Author
Owner

@github-actions[bot] commented on GitHub (May 3, 2024):

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

<!-- gh-comment-id:2091956361 --> @github-actions[bot] commented on GitHub (May 3, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3271
No description provided.