mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3048] Missing systemd folder #2437
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2437
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gensight on GitHub (Aug 6, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3048
Bug Description
I use FRP with my production AI system and tried to download [frp_0.44.0_linux_arm64.tar.gz] but am missing the systemd folder. I need this to run as a service. Please advise.
frpc Version
44.0
frps Version
44.0
System Architecture
linux/arm64
Configurations
basic port forwarding
Logs
No response
Steps to reproduce
...
Affected area
@Becods commented on GitHub (Aug 7, 2022):
a72259c604/conf/systemd/frpc.service (L1-L15)a72259c604/conf/systemd/frpc%40.service (L1-L15)a72259c604/conf/systemd/frps.service (L1-L14)a72259c604/conf/systemd/frps%40.service (L1-L14)@fatedier commented on GitHub (Aug 7, 2022):
There are many systemd issues or PRs and we have not enough resource to sovle it, so it was removed from the official release assets to avoid usage problems.
You can write your own systemd or other deploy files if needed.
We may provide deploy configs when we have active developers focus on this area.
@c04022004 commented on GitHub (Aug 8, 2022):
Was using the
systemdfiles along with older versions without much problem.Good to know about the reason behind the removal, completely understand your concerns.
Hope it can be put back soon.
@github-actions[bot] commented on GitHub (Sep 8, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.