Re: nwkq=N
> The manual page, aufs.5 is built by make. > Please make it. > I apologize for my ignorance, I didn't realize it's updated during make. Now I compiled it with 'make -f local.mk aufs.5' and I can see the default value of nwkq is 4. Thank you very much. Tomas M slax.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Re: nwkq=N
Tomas M: > I still can't find it. > In aufs.in.5 there is written: > default value is . The manual page, aufs.5 is built by make. Please make it. Junjiro Okajima - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Re: nwkq=N
[EMAIL PROTECTED] wrote: > Hi Tomas, > > Tomas M: >> would you please write some more info about nwkq parameter for aufs? >> At least, what is the default value, or what it is the >> 'special I/O request' you're refering to in man aufs.5 > > The default value is described in the manual. I still can't find it. In aufs.in.5 there is written: default value is . > And how about this one? > > +The special I/O requests from aufs include a part of copy-up, lookup, > +directory handling, pseudo-link and xino file operations. > +For example, Unix filesystems allow you to rmdir(2) which has no write > +permission bit, if its parent directory has write permission bit. In aufs, > the > +removing direcoty may or may not have whiteout or 'dir opaque' mark as its > +child. And aufs needs to unlink(2) them before rmdir(2). > +Therefore aufs delegates the actual unlink(2) and rmdir(2) to another kernel > +thread which has been created already and has a superuser privilege. > > Junjiro Okajima > I didn't update to latest CVS version, I'm sorry. Now I can see it's there, thank you very much! Tomas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Re: nwkq=N
Hi Tomas, Tomas M: > would you please write some more info about nwkq parameter for aufs? > At least, what is the default value, or what it is the > 'special I/O request' you're refering to in man aufs.5 The default value is described in the manual. And how about this one? +The special I/O requests from aufs include a part of copy-up, lookup, +directory handling, pseudo-link and xino file operations. +For example, Unix filesystems allow you to rmdir(2) which has no write +permission bit, if its parent directory has write permission bit. In aufs, the +removing direcoty may or may not have whiteout or 'dir opaque' mark as its +child. And aufs needs to unlink(2) them before rmdir(2). +Therefore aufs delegates the actual unlink(2) and rmdir(2) to another kernel +thread which has been created already and has a superuser privilege. Junjiro Okajima - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
nwkq=N
Hello, would you please write some more info about nwkq parameter for aufs? At least, what is the default value, or what it is the 'special I/O request' you're refering to in man aufs.5 Thank you very much. Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
