Key | Value |
---|---|
FileName | ./etc/logrotate.d/tcmu-runner |
FileSize | 177 |
MD5 | 269FD74EF8D287F5B8A4B7A6EB597DE3 |
SHA-1 | 25CC9ED3F71A265A5E009934725AE52393414A41 |
SHA-256 | 139D47DB37406F46FDB854CF70F5A0F2649541BDC3774FDEC2BAD65967C012D4 |
SSDEEP | 3:EJotQLuECFwFwyj2FsVDoo2FFZKeRqMClTvFHLKnNoJJFpsVQLA//GL:EJoiLuRww83p2FF0epaFrwQFpdLA/k |
TLSH | T1C2C0124B5419253474C9CD0E0A2525598992541759250915BF8EDBB44F1A972BE487E0 |
hashlookup:parent-total | 56 |
hashlookup:trust | 100 |
The searched file hash is included in 56 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 95216 |
MD5 | 164607AB4382775A153E1D63ABC3EE8A |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Freexian Packaging Team <team+freexian@tracker.debian.org> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.2-2~bpo10+1 |
SHA-1 | 0061B42BA13A92E99F3BFCA8C58A18D28B117333 |
SHA-256 | A5E46A33DF322736270D15114D752273E18412CD657F13A60EBCEDC556D24486 |
Key | Value |
---|---|
MD5 | F87C624414155D9F62FF73507F3F9051 |
PackageArch | x86_64 |
PackageDescription | A daemon that handles the complexity of the LIO kernel target's userspace passthrough interface (TCMU). It presents a C plugin API for extension modules that handle SCSI requests in ways not possible or suitable to be handled by LIO's in-kernel backstores. |
PackageMaintainer | Fedora Project |
PackageName | tcmu-runner |
PackageRelease | 2.fc32 |
PackageVersion | 1.5.2 |
SHA-1 | 00BA78A3D89B56AD4BFBF1450013E7F9F552DF5E |
SHA-256 | 026763BDA4B85207C2426879615AF560D0D7F200A64F74CE82BE40BBED32F960 |
Key | Value |
---|---|
FileSize | 101068 |
MD5 | E25454E9FB8CA29804E328C2EE4420D9 |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Freexian Packaging Team <team+freexian@tracker.debian.org> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.2-6 |
SHA-1 | 00BCBE4C114835A461FDFF63F4E898EADE8FA843 |
SHA-256 | 378D2ABC554F84F84F289D25CCAC5CBE53D9008D5F18DEDCAA24EA16AD4E05F5 |
Key | Value |
---|---|
FileSize | 89488 |
MD5 | 6AEAFC2DE2D171E9A8D785FF120BF158 |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.2-5ubuntu0.20.04.1 |
SHA-1 | 04A05CE678FC75E87C00CCBC1C154DCB6AE732C0 |
SHA-256 | E21359D504BC9FDE7A4AA1C91303A94912813FC21F5DC80AD4AFEFC937A873BF |
Key | Value |
---|---|
MD5 | CA8F72009E08C00F31AE3DD18F3E4C5A |
PackageArch | x86_64 |
PackageDescription | LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. |
PackageMaintainer | https://www.suse.com/ |
PackageName | tcmu-runner |
PackageRelease | 150400.1.5 |
PackageVersion | 1.5.4 |
SHA-1 | 128B028D6DF130F4CE761BDA601B45CD7DFCCF56 |
SHA-256 | 16AE496AE3BAE99572A6935370AF3E6DADD7490E3E8168EF0A85E9B2A44440E0 |
Key | Value |
---|---|
FileSize | 98036 |
MD5 | B09954B66A91542A1F8E1C829AA64C16 |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.4-2 |
SHA-1 | 13D69190D0896B19C8E19270FE840B1089E1D764 |
SHA-256 | D29BF1860EBD1E160351A26F828DD503681ABE40398FAFD1B13928536E37E316 |
Key | Value |
---|---|
FileSize | 82780 |
MD5 | 6482D98A731B81B1DD6A0D425BE21541 |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Freexian Packaging Team <team+freexian@tracker.debian.org> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.2-2~bpo10+1 |
SHA-1 | 142C69D596378D3617B80F68DDCE670B0C1C4626 |
SHA-256 | C2A62E2E4D0DC1EDEF8F2A2297E88D7ABBF9552484041EE571885054415A3B49 |
Key | Value |
---|---|
FileSize | 90616 |
MD5 | 77A662614F6243A50D4BA0D1CE665A14 |
PackageDescription | Daemon that handles the userspace side of the LIO TCM-User backstore LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if one want to get fancier with the capabilities of the device one is emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. . The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that one would like to avoid each userspace handler having to write boilerplate code. . tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. . This is the daemon package |
PackageMaintainer | Freexian Packaging Team <team+freexian@tracker.debian.org> |
PackageName | tcmu-runner |
PackageSection | admin |
PackageVersion | 1.5.2-6 |
SHA-1 | 1588615028455C3AD1695809E7EB310A70791832 |
SHA-256 | E0FB7E920D220D7F701D98A635A1A4A4B7BDFF9B402F99D6BF3CF938613C3A8A |
Key | Value |
---|---|
MD5 | 4969E8C85B7CB3C31F831E7057D28B68 |
PackageArch | x86_64 |
PackageDescription | LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like. |
PackageName | tcmu-runner |
PackageRelease | 39.18 |
PackageVersion | 1.5.4 |
SHA-1 | 17AE41F0F53C8ADA6E218E0B46702A4E7E31E58D |
SHA-256 | 2DE1A3868BB579548A6D556800C64ED0490FF3D4C3218CBC9A3CF486F98D489A |
Key | Value |
---|---|
MD5 | EFA4A3664CC2E2DC136BF84042A55FA3 |
PackageArch | aarch64 |
PackageDescription | A daemon that handles the complexity of the LIO kernel target's userspace passthrough interface (TCMU). It presents a C plugin API for extension modules that handle SCSI requests in ways not possible or suitable to be handled by LIO's in-kernel backstores. |
PackageMaintainer | Fedora Project |
PackageName | tcmu-runner |
PackageRelease | 8.fc34 |
PackageVersion | 1.5.2 |
SHA-1 | 1A9EFDDA9F5630B6A3DEB06C41B4755E4B12F2BC |
SHA-256 | 010463FFAD119A3C2E477511A598FDF9C0A671383A74BFBE110630B91EA1A5BC |