| Summary: | Incorrect PID printed in the glusterfs log header | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Gururaj K <guru> |
| Component: | logging | Assignee: | Vikas Gorur <vikas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0.2 | CC: | gluster-bugs, rabhat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Vikas Gorur
2009-06-08 09:48:38 UTC
The log header prints the pre-daemon pid which does not match the pid seen if we do a ps. Infact the log file prints the "correct" pid as well: PID : 12311 .. .. [2009-06-08 11:57:12] D [glusterfsd.c:1179:main] glusterfs: running in pid 12312 |