Your message dated Fri, 25 Mar 2011 02:43:30 +0100
with message-id <[email protected]>
and subject line Re: Bug#526647: zsh won't accept vaild commands when used 
through ssh
has caused the Debian Bug report #526647,
regarding zsh won't accept vaild commands when used through ssh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
526647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526647
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zsh
Version: 4.3.6-6
Severity: normal


$ ssh somesudoer@host sudo egrep '<=|=>' /var/log/exim4/mainlog
zsh:1: datei oder Verzeichnis nicht gefunden: =
zsh:1: keine Berechtigung: /var/log/exim4/mainlog

$ ssh root@host egrep '<=|=>' /var/log/exim4/mainlog
zsh:1: datei oder Verzeichnis nicht gefunden: =
zsh:1: command not found: =

Sorry for the german text, I could not find a way to get LANG="C"
placed correctly.

The fist says fist «file or directory not found: =» and claims I have
no right to access /var/log/exim4/mainlog which is incorrect when using
sudo.

The second fist has the same message and then claims it can't find the
command '='

Regards

        Christoph

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages zsh depends on:
ii  libc6                     2.7-18         GNU C Library: Shared libraries
ii  libcap2                   2.11-2         support for getting/setting POSIX.
ii  libncursesw5              5.7+20081213-1 shared libraries for terminal hand

Versions of packages zsh recommends:
ii  libpcre3                      7.6-2.1    Perl 5 Compatible Regular Expressi

Versions of packages zsh suggests:
pn  zsh-doc                       <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

Christoph Egger wrote:
> $ ssh somesudoer@host sudo egrep '<=|=>' /var/log/exim4/mainlog
> zsh:1: datei oder Verzeichnis nicht gefunden: =
> zsh:1: keine Berechtigung: /var/log/exim4/mainlog
> 
> $ ssh root@host egrep '<=|=>' /var/log/exim4/mainlog
> zsh:1: datei oder Verzeichnis nicht gefunden: =
> zsh:1: command not found: =

First: This is definitely no zsh issue as this happens with any login
shell (just verified it with bash):

bash: /var/log/exim4/mainlog: Permission denied
bash: =: No such file or directory

Second: This is no bug at all but just the failure to properly quote
your command when passing it to some remote host via ssh.

> The fist says fist «file or directory not found: =» and claims I have
> no right to access /var/log/exim4/mainlog which is incorrect when using
> sudo.

No, these are completely valid and correct error messages: 

1) somesudoer has no write permissions to /var/log/exim4/mainlog

> The second fist has the same message and then claims it can't find the
> command '='

Which is correct again:

2) You can't read STDIN from a non-existent file called "=".
3) You can't pipe to the non-existent command "=".

Clint Adams wrote:
> I'm not sure why you think this is a zsh bug; ssh quoting requirements
> are notoriously annoying.

No they are just consequent:

ssh doesn't get passed any single or double quotes from shell if they
were used for quoting because the shell strips quoting characters. And
it passes what it gets to the login shell on the remote site which
gets interpreted a second time. Which is what you want.

> Try something like
> 
> ssh root@host "egrep '<=|=>' /var/log/exim4/mainlog"

Exactly. Because else

# egrep < = | = > /var/log/exim4/mainlog

would be executed on the remote system which doesn't make any sense
but causes the above mentioned error messages.

Closing this bug report herewith as it is no bug.

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


--- End Message ---

Reply via email to