You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
FileTrove will find artifacts that are not files nor directories, but maybe relevant and the information should not be lost, e.g. named pipes.
type = {named_pipe, socket, block_device, link, ...}.
and we can use
b block (buffered) special
c character (unbuffered) special
[d directory]
p named pipe (FIFO)
[f regular file]
l symbolic link [?]
s socket
D door (Solaris)
as type labels. These match mostly the string representations of file mode bits.
For some special cases like "System Volume Information" on NTFS in combination with non-native NTFS operating systems filepath.WalkDir might fail. These cases should not cancel the run and write these types also into the artifacts table.
Is your feature request related to a problem? Please describe.
FileTrove will find artifacts that are not files nor directories, but maybe relevant and the information should not be lost, e.g. named pipes.
The idea is to create a table with this schema
where
and we can use
as type labels. These match mostly the string representations of file mode bits.
See also: #112 (comment)
The text was updated successfully, but these errors were encountered: