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.)