From: Luis F. <lui...@gm...> - 2008-11-24 15:53:05
|
On Mon, Nov 24, 2008 at 1:12 PM, Santiago <sa...@gm...> wrote: > Hello, > > On Mon, Nov 24, 2008 at 14:49, Luis Furquim <lui...@gm...> wrote: >> On Mon, Nov 24, 2008 at 11:56 AM, Santiago <sa...@gm...> wrote: >> > No prob. I decided to parse the options by myself, so now I know where I >> > am. My first try is online: http://sourceforge.net/projects/iafs/ >> >> Take a look at these command line argumets parsing from Miklos: >> ... > > Thank you for the samples, but I'm sorry, I don't really understand, why you > sent it. My option-parsing is already working - and when I start the fs from > commandline, there are no probs. > I don't have empty arguments. > > I think, there will be a problem with the fact, that I use 2 paths in fstab: > iafs#/first/path /second/path fuse noauto,defaults 0 0 > > From the tests I did, the argument passing works. Currently I don't have any > idea, where the error comes from. > > I looked at sshfs and ntfs-3g for tutorial purpose. I passed to them because your issue were in this area: parsing the command line. You say it works, but you say it doesn't work *when* they are passed via fstab. So, when you use fstab, the options come as arguments of the "-o" option. As I thought you would have to change your code to handle it (I downloaded your code, but really didn't look your code at a deep detail level), I assumed it could be a good idea to look at the standard FUSE tools to make it. >> >> > 2. when I have two fstab entries of my fuse-fs mt-enabled - are they >> >> > separate processes, or do they share the globals? >> >> >> >> They will be separate processes. >> > >> > That's good. >> > >> > Currently my stuff is not safe for multithreading, but I'm working on >> > that item. >> >> Beware! Even with just one mount of your filesystem, your function >> callbacks may be called in different threads! To make sure they will be >> serialized you must use the '-s' fuse option. > > Well, I think, my functions are reentrant, but I don't know yet, how I can > prevent fuse from creating threads (only for certain time). > When I change the underlaying filesystem, I'd like to block fuse, until the > new filesystem is mounted. > When I got this, I think my stuff will be thread safe. So, you have to use semaphores. You will not block FUSE, but will block your callbacks. Best Regards! -- Luis Otavio de Colla Furquim Não alimente os pingos Don't feed the tribbles http://www.furquim.org/chironfs/ |