From: Clint Adams <schizo@debian.org>
To: zsh-workers@sunsite.dk
Cc: Vincent Lefevre <vincent@vinc17.org>, 221875-forwarded@bugs.debian.org
Subject: Re: zsh sometimes sets $PWD to "." when executed
Date: Fri, 23 Jul 2004 13:40:44 -0400 [thread overview]
Message-ID: <20040723174044.GA10121@scowler.net> (raw)
In-Reply-To: <20031224182536.GU1501@ay.nerim.net>
Is this still happening? What does "pwd -P" return in such
circumstances?
> I'm reassigning the bug to zsh, as I now know that the problem doesn't
> come from screen. However it has always occurred in screen (but this
> isn't necessarily meaningful).
>
> This time, the bug occurred on another account (but still in screen and
> still in an NFS directory). Instead of opening a new screen window, I did
> the following, where z is:
>
> alias z='if [[ -o login ]]
> then exec $SHELL -l;
> else exec $SHELL;
> fi'
>
> liberte:~/oldtests[130]> z <18:13:16
> zshenv...
> zshrc...
> Shell level: 2 (login shell)
> The tty is frozen
> zlogin...
> liberte:.> pwd <18:13:19
> .
> liberte:.> ll /proc/$$ <18:14:00
> total 0
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 cantmove
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 cmdline
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 cpu
> lrwxrwxrwx 1 vlefevre lip 0 Dec 24 18:14 cwd -> /home/vlefevre/
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 disclosure
> -r-------- 1 vlefevre lip 0 Dec 24 18:14 environ
> lrwxrwxrwx 1 vlefevre lip 0 Dec 24 18:14 exe -> /home/vlefevre/bin-i386/zsh*
> dr-x------ 2 vlefevre lip 0 Dec 24 18:14 fd/
> --w--w--w- 1 vlefevre lip 0 Dec 24 18:14 goto
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 lock
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 maps
> -rw------- 1 vlefevre lip 0 Dec 24 18:14 mem
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 migfilter
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 miggroup
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 mignodes
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 migpolicy
> --w------- 1 vlefevre lip 0 Dec 24 18:14 migrate
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 mounts
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 nmigs
> lrwxrwxrwx 1 vlefevre lip 0 Dec 24 18:14 root -> //
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 selected
> -rw-r--r-- 1 vlefevre lip 0 Dec 24 18:14 sigmig
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 stat
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 statm
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 status
> -r--r--r-- 1 vlefevre lip 0 Dec 24 18:14 where
>
> Both $PWD and the cwd are incorrect. They should both have been
> "/home/vlefevre/oldtests".
>
> Or is it a bug in the Linux kernel for the cwd part? FYI, for both
> machines where the bug occurred, the kernel is respectively 2.4.20
> and 2.4.22.
next parent reply other threads:[~2004-07-23 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031224182536.GU1501@ay.nerim.net>
2004-07-23 17:40 ` Clint Adams [this message]
2004-07-23 18:03 ` Bart Schaefer
2004-07-23 18:34 ` Vincent Lefevre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040723174044.GA10121@scowler.net \
--to=schizo@debian.org \
--cc=221875-forwarded@bugs.debian.org \
--cc=vincent@vinc17.org \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).