We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Doesn't running p4d -d through daemon on this line create an extraneous process that immediately forks off another one?
p4d -d
daemon
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:
$p4start
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.
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
Apparently I need to fix my notifications as well, only just noticed this. Will open a PR when I get a chance.
rohanliston
No branches or pull requests
Doesn't running
p4d -d
throughdaemon
on this line create an extraneous process that immediately forks off another one?Currently:
After changing the value of
$p4start
to justp4d
:Happy to pull request if that's the case.
The text was updated successfully, but these errors were encountered: