| Summary: | The perforce proxy don't start/stop properly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gisle Aas <gisle> |
| Component: | [OLD] Development | Assignee: | Stuart Herbert (RETIRED) <stuart> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | haavardw, halcy0n |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
The fix I made to make perfore-proxy {start,stop} work for me
init.d-perforce-proxy.patch |
||
Created attachment 35244 [details, diff]
The fix I made to make perfore-proxy {start,stop} work for me
The patch is actually reversed. Sorry about that. Created attachment 84449 [details, diff]
init.d-perforce-proxy.patch
I believe the line that stripped out the -d and -r arguments was correct, but the stop() function was obviously wrong. I propose this patch instead that uses start-stop-daemon --stop which should do the same trick, but should be easier to maintain.
I'm no longer maintaining this package. No-one else has stepped up and volunteered to maintain it; we will be dropping Perforce from Portage shortly. Best regards, Stu |
It looks like the p4p init file is just copies from the p4d init file. I'll attach a patch that fixes this problem for me. Reproducible: Always Steps to Reproduce: 1. /etc/init.d/perforce-proxy start 2. access perforce via the proxy 3. look at /var/log/perforce-proxy Actual Results: erforce proxy error: Date 2004/07/12 10:52:52: Operation: flush2 can't make directory for depot/depot/main/Apps/PDK/src/DynDLL/Makefile,v mkdir: depot: Permission denied Expected Results: No error message.