Re: [fuse-devel] Re: fuseiso: Transport endpoint not connected

[Miklos S. <mi...@sz...>]

> is there another way to do it ?
> My filesystem handles itself the "-d" flag (special debug processing) 
> and always gives "-f" to fuse, along with the other arguments. It means 
> that relative directories are always correctly handled. Now with this 
> patch, this will no longer be possible.

I think it shouldn't be too hard to either

  - omit the daemon/chdir step (*)

  - save/restore the cwd as discussed earlier

(*) this is almost possible now, since fuse_main() is really just a
series of calls to:

  fuse_parse_cmdline()
  fuse_mount()
  fuse_new()
  fuse_demonize()
  fuse_set_signal_handlers()
  fuse_loop()/fuse_loop_mt()
  fuse_unmount()
  fuse_destroy()


Of this the only ones currently not exported are fuse_daemonize() and
fuse_get_session() needed for fuse_set_signal_handlers().

If those are exported then it becomes quite easy to do custom
initializations.  The fuse_setup() and fuse_teardown() can also be
deprecated and eventually removed in fuse-3.0

Miklos