Solaris 10 - ZSH displays a . when pwd on nfs mount
Solaris / OpenSolarisThis forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
now those folders are then symlinks to something say /u/data1 -----> /v/host/zldata01
/u/data2 -----> /v/host/zldata02
/u/data3 -----> /v/host/zldata03
/u/data4 -----> /v/host/zldata04
The issue that I'm seeing which is very weird. Is when I go into folder /u/data4/folder/ and run #pwd it returns with #. instead of the full path. This weirdness is only present when using the zsh shell, and appears in both the symlink and the absolute path. And whats even worse is its only on data04. All the others work just as expected. Some things I have noticed is if I run a truss -o test.txt pwd it actually returns the correct path and not a dot. My collegue ran a truss and managed to get an error or 79 which I found out is a overrun of the buffer declaring a variable. Usually when there is a large file involved. Except this is a directory not a file and then name scheme is pretty simple. All the mounts are the same. The underlying file system is xfs. There are no weird errors in messages and we havent rebooted or anything. I have been unable to reproduce this in a lab enviroment either.
by default pwd is a shell builtin, but also a binary executable exists (that is /bin/pwd). you can check it with the command type pwd. The builtin has some options and also can be ruled by environment variables.
pwd [ -rLP ]
Print the absolute pathname of the current working directory. If
the -r or the -P flag is specified, or the CHASE_LINKS option is
set and the -L flag is not given, the printed path will not
contain symbolic links.
So its the pwd shell version from zsh thats the issue. I'll have to investigate more to find out why. so when I run a truss on the command which is it running? The shell or the binary? I assume the binary since running truss pwd did produce an output as expected. That also isolates it even further to zsh since auto complete does not appear to work. on the folders inside.
Okay very interestingly I have found a coloration with what you mentioned and the buffer over flow my colleague found. Which it all makes sense now. ZSH is a 32bit version and the xfs file system installed is inode64. So it now makes sense that ZSH built in shell command is erroring out when trying to do a listing of the current directory. the next question tho is what to do lol. don't wanna redo everything. So I'll have to figure out something.