[GH-ISSUE #643] Background client on start #502

New issue

Closed

opened 2026-05-05 12:19:42 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 12:19:42 -06:00

Owner

Originally created by @travisghansen on GitHub (Feb 25, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/643

I'm looking to use the client in a CI environment. Ideally I'd be able to start the client and have it exit (cleanly or not) immediately so the subsequent series of commands could be run which an understanding of tunnel up/down. In my case backgrounding and doing a port check isn't super-helpful as I'm using the http type.

Originally created by @travisghansen on GitHub (Feb 25, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/643 I'm looking to use the client in a CI environment. Ideally I'd be able to start the client and have it exit (cleanly or not) immediately so the subsequent series of commands could be run which an understanding of tunnel up/down. In my case backgrounding and doing a port check isn't super-helpful as I'm using the http type.

gitea-mirror closed this issue

2026-05-05 12:19:42 -06:00

gitea-mirror commented

2026-05-05 12:19:44 -06:00

Author

Owner

@fatedier commented on GitHub (Feb 26, 2018):

Try nohup to let client run on background?
Run frpc -c ./frpc.ini status and you can get all status of proxies.

@fatedier commented on GitHub (Feb 26, 2018): 1. Try `nohup` to let client run on background? 2. Run `frpc -c ./frpc.ini status` and you can get all status of proxies.

gitea-mirror commented

2026-05-05 12:19:45 -06:00

Author

Owner

@travisghansen commented on GitHub (Feb 27, 2018):

Yeah, I was looking into that. Not ideal but possible, thanks for the pointer.

@travisghansen commented on GitHub (Feb 27, 2018): Yeah, I was looking into that. Not ideal but possible, thanks for the pointer.

gitea-mirror commented

2026-05-05 12:19:46 -06:00

Author

Owner

@yanggis commented on GitHub (Feb 27, 2018):

try supervisor

@yanggis commented on GitHub (Feb 27, 2018): try supervisor

gitea-mirror commented

2026-05-05 12:19:46 -06:00

Author

Owner

@travisghansen commented on GitHub (Feb 28, 2018):

Thanks for the suggestion. Supervisor doesn't fit the need here really and would be overkill. I'm sure I can find a solution using nohup or the like...just would be nice to have a daemonize option that could exit non zero if tunnel(s) failed.

@travisghansen commented on GitHub (Feb 28, 2018): Thanks for the suggestion. Supervisor doesn't fit the need here really and would be overkill. I'm sure I can find a solution using nohup or the like...just would be nice to have a daemonize option that could exit non zero if tunnel(s) failed.