Optional
chrootOptional
chroots?: Set<EncryptedFS>Optional
crypto?: { Readonly
[initProtected
_cwdReadonly
blockProtected
Optional
chrootProtected
chrootsProtected
Optional
cryptoProtected
dbProtected
dbProtected
fdProtected
iProtected
iProtected
loggerProtected
rootProtected
_openOptional
tran: DBTransactionOptional
mode: numberProtected
checkChecks the permissions fixng the current uid and gid. If the user is root, they can access anything.
Optional
callback: CallbackOptional
options: OptionsStreamOptional
options: OptionsStreamOptional
callback: CallbackOptional
callback: CallbackOptional
callback: CallbackOptional
callback: CallbackOptional
callback: CallbackOptional
len: numberOptional
callback: CallbackProtected
getProcesses data types and collapses it to a Buffer. The data types can be Buffer or Uint8Array or string.
Protected
getTakes a default set of options, and merges them shallowly into the user provided options. Object spread syntax will ignore an undefined or null options object.
Optional
encoding?: BufferEncodingOptional
flag?: stringOptional
mode?: numberOptional
recursive?: booleanOptional
options: BufferEncoding | OptionsProtected
getProcesses path types and collapses it to a string. The path types can be string or Buffer or URL.
Protected
getOptional
seekFlags: numberOptional
options: OptionsMakes an inode
This call must handle concurrent races to create the inode
Optional
mode: numberProtected
navigateNavigates the filesystem tree from root. You can interpret the results like: target == null => Non-existent segment name === '' => Target is at root name === '.' => dir is the same as target name === '..' => dir is a child directory
Protected
navigateNavigates the filesystem tree from a given directory. You should not use this directly unless you first call _navigate and pass the remaining path to _navigateFrom. Note that the pathStack is always the full path to the target.
Each navigateFrom call usually has its own transaction context
It does not preserve transaction context on recursive calls
to this.navigate
or this.navigateFrom
.
This is because navigation on from a particular inode is a
self-contained operation.
Callers must pass an existing transaction context if they are navigating
from an inode that was just created within that transaction context, this
is necessary because otherwise there will be a deadlock when
this.navigateFrom
starts their own transaction context on that inode
Optional
tran: DBTransactionOptional
mode: numberProtected
parseParses and extracts the first path segment.
Optional
offset: numberOptional
length: numberOptional
position: numberMakes a symlink
This call must handle concurrent races to create the symlink inode
Optional
len: numberOptional
offsetOrPos: numberOptional
lengthOrEncoding: string | numberOptional
position: numberStatic
createOptional
blockOptional
fdOptional
fresh?: booleanOptional
iOptional
logger?: LoggerOptional
umask?: numberOptional
blockOptional
fdOptional
fresh?: booleanOptional
iOptional
logger?: LoggerOptional
umask?: numberGenerated using TypeDoc
This call must handle concurrent races to create the file inode