unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Kraus <daniel@kraus.my>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp rclone
Date: Sun, 25 Nov 2018 13:02:44 +0100	[thread overview]
Message-ID: <87va4l1i1n.fsf@gmx.de> (raw)
In-Reply-To: <87sgzp75od.fsf@kraus.my> (Daniel Kraus's message of "Sun, 25 Nov 2018 19:33:22 +0800")

Daniel Kraus <daniel@kraus.my> writes:

> Hi!

Hi Daniel,

> Result is the same though.
> No such directory in eshell (is that even supposed to work?)
> and empty list in dired.
>
> Attached is the tramp log (verbose set to 10) where
> I first tried to open `/rclone:drive:` (drive is my remote name)
> and then `/rclone:drive:/skor`.

Strange. The log doesn't show any external command but

> 19:22:26.834686 tramp-call-process (6) # ‘rclone about drive: --full’ nil *tramp/rclone drive*
> 19:22:27.355841 tramp-call-process (6) # 0
> Total:   128849018880
> Used:    452653677
> Free:    79889759394
> Trashed: 4593779
> Other:   48506605809

That works as expected, and it is a proof that your storage "drive" is
configured properly.

But I'm missing a mount operation.

Could you pls check whether rclone is running for mount? What do you get
with

# ps -eaf | grep rclone

Furthermore, how does /tmp/tramp.rclone.drive look like? It must be a
directory, and there must be files from your remote "drive".

If there is an rclone process running, pls unmount that directory,
possibly you must do it with "fusermount -u /tmp/tramp.rclone.drive".
The directory must be empty then, and the rclone process must have been
killed. Delete the directory, and run "emacs -Q" after that again, and
show the logs.

(Maybe there is an error in the mount operation as implemented in
tramp-rclone.el, will check.)

> Thanks,
>   Daniel

Best regards, Michael.



  reply	other threads:[~2018-11-25 12:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 13:16 Tramp rclone Michael Albinus
2018-11-24 13:56 ` Eli Zaretskii
2018-11-25  3:01 ` John Wiegley
2018-11-25  8:38   ` Michael Albinus
2018-11-26  1:39   ` Richard Stallman
2018-11-26  3:39     ` Eli Zaretskii
2018-11-26 20:50       ` Richard Stallman
2018-11-27 16:00         ` Michael Albinus
2018-11-28 11:25           ` Michael Albinus
2018-11-29  0:19             ` Richard Stallman
2018-11-30  9:46               ` Michael Albinus
2018-11-30 22:44                 ` Richard Stallman
2018-11-26 19:15     ` Michael Albinus
2018-11-27 22:55       ` Richard Stallman
2018-11-25  3:56 ` Daniel Kraus
2018-11-25  8:43   ` Michael Albinus
2018-11-25 11:33     ` Daniel Kraus
2018-11-25 12:02       ` Michael Albinus [this message]
2018-11-26 12:35         ` Daniel Kraus
2018-11-26 18:55           ` Michael Albinus
2018-11-27  9:44             ` Daniel Kraus
2018-11-27 12:18               ` Michael Albinus
2018-11-27 13:14                 ` Daniel Kraus
2018-11-27 13:32                   ` Michael Albinus

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87va4l1i1n.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=daniel@kraus.my \
    --cc=emacs-devel@gnu.org \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).