emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tramp mode not working on OSX with dev HEAD


From: Michael Albinus
Subject: Re: tramp mode not working on OSX with dev HEAD
Date: Mon, 08 Mar 2010 09:00:21 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (gnu/linux)

address@hidden (Randal L. Schwartz) writes:

>>>>>> "Michael" == Michael Albinus <address@hidden> writes:
>
> Michael> Start a fresh Emacs via "emacs -Q". Eval (setq tramp-verbose 8)
>
> Michael> The resulting buffer *debug tramp/scp address@hidden shall give the 
> required
> Michael> information.
>
> Trying to find-file on /root/SAVE on opensolaris 2009.06:

The traces do not look complete. Did you start a fresh Emacs, and did
you copy all traces? I need traces from a clean Tramp run!

> ;; GNU Emacs: 23.1.93.4 Tramp: 2.1.18-pre -*- mode: outline; -*-
> 14:37:47.842360 tramp-flush-file-property (8) # /root/
> 14:37:47.844978 tramp-get-file-property (8) # /root/SAVE 
> file-attributes-integer (nil 1 0 0 (19182 39028) (19182 39028) (19182 39028) 
> 3779 -rw-r--r-- nil (3 . 39269) (-1 . 0))
> 14:37:47.847136 tramp-get-file-property (8) # /root/SAVE file-exists-p t
> 14:37:47.848257 tramp-get-file-property (8) # /root/SAVE file-exists-p t

This is an indication, that the traces do not start from the
beginning. Tramp reads from its cache.

> 14:37:47.855036 tramp-maybe-open-connection (6) # /bin/sh
> 14:37:47.856346 tramp-maybe-open-connection (3) # Waiting 60s for local shell 
> to come up...
> 14:37:47.856866 tramp-get-connection-property (7) # check-remote-echo nil
> 14:37:47.857133 tramp-get-connection-property (7) # check-remote-echo nil
> 14:37:47.858787 tramp-get-connection-property (7) # check-remote-echo nil
> 14:37:47.859034 tramp-get-connection-property (7) # check-remote-echo nil
> 14:37:47.859305 tramp-wait-for-regexp (6) #
>
> Process *tramp/scp insightcruises.com* exited abnormally with code 255
> #$

Oops, what's that? When Tramp calls *locally* "/bin/sh", this shouldn't
happen. And "#$" looks like a prompt from a previous run.

Again, I cannot analyze these traces. Please start a fresh "emacs -Q",
as I have said last email.

Best regards, Michael.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]