Skip to content
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

Running p4d -d through daemon redundant? #2

Open
rohanliston opened this issue May 31, 2016 · 2 comments
Open

Running p4d -d through daemon redundant? #2

rohanliston opened this issue May 31, 2016 · 2 comments
Assignees
Labels

Comments

@rohanliston
Copy link

rohanliston commented May 31, 2016

Doesn't running p4d -d through daemon on this line create an extraneous process that immediately forks off another one?

Currently:

> ps aux | grep p4d
perforce  7213  0.0  0.0  20024   400 ?        S    21:16   0:00 daemon -u perforce -- p4d -d
perforce  7214  0.0  0.0      0     0 ?        Z    21:16   0:00 [p4d] <defunct>
perforce  7215  0.0  0.1  23004  1088 ?        S    21:16   0:00 p4d -d

After changing the value of $p4start to just p4d:

> ps aux | grep p4d
perforce  7162  0.0  0.0  20024   400 ?        S    21:14   0:00 daemon -u perforce -- p4d
perforce  7163  0.0  0.2  22956  2356 ?        S    21:14   0:00 p4d

Happy to pull request if that's the case.

@Allar
Copy link
Owner

Allar commented Nov 5, 2016

I really gotta fix my notifcations.

Please make a pull request if everything is still good. You most likely know more than me about this.

@rohanliston
Copy link
Author

Apparently I need to fix my notifications as well, only just noticed this. Will open a PR when I get a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants