I see, I must have missed that! :) Well, thanks for taking a look and responding anyways.
BTW, my use-case, and reason that I need the mount to exit when done mounting is that I'm using it in a backup script: I mount, backup, and then unmount. The FS doesn't stay mounted outside of the backup script. My regards, Ido On Thursday, September 4, 2014 3:08:05 AM UTC+3, Nikolaus Rath wrote: > > On 09/03/2014 01:25 PM, Ido wrote: > > Hello, > > > > I've been using s3ql for about a year now, and I'm very happy / excited > > about it! Unfortunately, the recent upgrade seems to hang it on my > system. > > > > This is what I'm getting: > >> sudo mount.s3ql --cachesize=5000000 --authfile=[...] [s3_dest] > > [mount_root] > > Using 8 upload threads. > > Autodetected 499944 file descriptors available for cache entries > > Using cached metadata. > > Mounting filesystem... > > > > And then it just hangs there... > > > > Any ideas? > > This was a deliberate change. From the changelog: > > * mount.s3ql no longer daemonizes on its own. With a modern init > system this should no longer be necessary, and when running > mount.s3ql from the command line the shell can be used to put the > process into background. > > > I have since learned that many people want this feature though, so this > change will be reverted in the next release. > > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« > -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
