| Summary: | Broken symbolic link when relative path is given for a log file | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sachidananda Urs <sac> |
| Component: | logging | Assignee: | Basavanagowda Kanur <gowda> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | aavati, gluster-bugs, vinayak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTA | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Basavanagowda Kanur
2009-07-21 10:56:51 UTC
When glusterfs is started with --run-id option by giving relative path for the log file, the symbolic link is broken. For eg: ================================================================ /opt/glusterfs/2.0.4/sbin/glusterfsd -f /home/sac/work/volfiles/nufa/nufa.vol -l ../home/sac/work/logs/2.0.4/nufa.f1.log --run-id nufatest /mnt/nufa/ Then a symbolic link is created under ~sac/work/logs/2.0.4/ as: nufa.f1.log -> ../home/sac/work/logs/2.0.4/nufa.f1.log.20090721.182334.23147 ================================================================ Which is obviously broken. Where as the link has to be: nufa.f1.log -> nufa.f1.log.20090721.182334.23147 Since both are created in same directory. This works fine when the absolute path is given. Please mark bugs as 'fixed' only after the bug gets commented by the scripts that the proposed patch has been committed to the repository PATCH: http://patches.gluster.com/patch/830 in master (glusterfsd: handle logfile path specification appropriately.) |