search for: pseudofil

...BTW, I'm not sure it's necessary to escape the #. I never tried it without. Also note that it flattens the remote host's mount tree into a single filesystem - so things like /proc look like they are in the same filesystem as /. This can lead to backing up /proc's contents (many pseudofiles), if you don't exclude it, even if you use rsync's -x option. On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync <rsync at lists.samba.org> wrote: > > I still stuck with these errors > > packet_write_wait: Connection to 192.168.10.43 port 22: Broken pipe > rsync: c...

...the complete operation of programs such as ps(1) and w(1). The Linux process file system, linprocfs(5), emulates a subset of Linux's process file system and is required for the complete operation of some Linux binaries. II. Problem Description The implementation of the /proc/curproc/cmdline pseudofile in the procfs(5) file system on FreeBSD 4.x and 5.x, and of the /proc/self/cmdline pseudofile in the linprocfs(5) file system on FreeBSD 5.x reads a process' argument vector from the process address space. During this operation, a pointer was dereferenced directly without the necessary valida...

...the complete operation of programs such as ps(1) and w(1). The Linux process file system, linprocfs(5), emulates a subset of Linux's process file system and is required for the complete operation of some Linux binaries. II. Problem Description The implementation of the /proc/curproc/cmdline pseudofile in the procfs(5) file system on FreeBSD 4.x and 5.x, and of the /proc/self/cmdline pseudofile in the linprocfs(5) file system on FreeBSD 5.x reads a process' argument vector from the process address space. During this operation, a pointer was dereferenced directly without the necessary valida...

...t's necessary to escape the #. I never tried it without. > > Also note that it flattens the remote host's mount tree into a single > filesystem - so things like /proc look like they are in the same > filesystem as /. This can lead to backing up /proc's contents (many > pseudofiles), if you don't exclude it, even if you use rsync's -x > option. > > On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync > <rsync at lists.samba.org> wrote: >> >> I still stuck with these errors >> >> packet_write_wait: Connection to 192.168.10.4...

...cks. These could also prove useful to implement my "Feature #1044: ZFS: Allow specifying minimum dataset/metaslab block size AND alignment" posted in https://www.illumos.org/issues/1044 Industry examples of grouped metadata could include copies of the FAT table in FAT/pcfs, and the $MFT pseudofile on NTFS. Difference is that ZFS metadata size is dynamic, so metadata regions should not rely on any predefined sizes. If this feature is not yet present, is it difficult or unreasonable for some reason to add one? Thanks, //Jim

...ape the #. I never tried it > without. >> >> Also note that it flattens the remote host's mount tree into a single >> filesystem - so things like /proc look like they are in the same >> filesystem as /. This can lead to backing up /proc's contents (many >> pseudofiles), if you don't exclude it, even if you use rsync's -x >> option. >> >> On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync >> <rsync at lists.samba.org> wrote: >>> >>> I still stuck with these errors >>> >>> packet_write_w...

...the #. I never tried it > without. >> >> Also note that it flattens the remote host's mount tree into a single >> filesystem - so things like /proc look like they are in the same >> filesystem as /. This can lead to backing up /proc's contents (many >> pseudofiles), if you don't exclude it, even if you use rsync's -x >> option. >> >> On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync >> <rsync at lists.samba.org> wrote: >>> >>> I still stuck with these errors >>> >>> packet_write...