Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we make Srs start with a config user/group to start #1111

Closed
Tiger1314 opened this issue Apr 9, 2018 · 4 comments
Closed

Can we make Srs start with a config user/group to start #1111

Tiger1314 opened this issue Apr 9, 2018 · 4 comments
Assignees
Labels
EnglishNative This issue is conveyed exclusively in English. Enhancement Improvement or enhancement. Feature It's a new feature. good first issue Easy to fix issues, good for newcomers
Milestone

Comments

@Tiger1314
Copy link

Tiger1314 commented Apr 9, 2018

As we know Nginx sub process can be config with defined user, like below

example:
user nobody nobody;
worker_processes auto;

so we want the SRS also have the ability to do that to help us easy depoy same process in the same VM or container

@winlinvip winlinvip added Enhancement Improvement or enhancement. Feature It's a new feature. labels Aug 4, 2018
@winlinvip winlinvip added this to the srs 3.0 release milestone Aug 4, 2018
@winlinvip
Copy link
Member

There is a workaroud, you can use a specific user to run SRS:

sudo su nobody -c /etc/init.d/srs start

SRS3 may support this feature, for security reason.

@thegobot
Copy link

  • need

@winlinvip
Copy link
Member

Plan in SRS4.

@winlinvip winlinvip self-assigned this Aug 23, 2021
@winlinvip winlinvip added the good first issue Easy to fix issues, good for newcomers label Jan 17, 2022
@winlinvip winlinvip modified the milestones: 5.0, 6.0 Jan 2, 2023
@winlinvip
Copy link
Member

Plan in SRS 6

@ossrs ossrs locked and limited conversation to collaborators Jul 18, 2023
@winlinvip winlinvip converted this issue into discussion #3655 Jul 18, 2023
@winlinvip winlinvip added the EnglishNative This issue is conveyed exclusively in English. label Jul 28, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
EnglishNative This issue is conveyed exclusively in English. Enhancement Improvement or enhancement. Feature It's a new feature. good first issue Easy to fix issues, good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants