Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/smmap/util.py |
FileSize | 7927 |
MD5 | 8D9C70379576571279B2E879EF1C16F9 |
SHA-1 | 2254B3B984854F06230F1FBFA5C59FFA3C9C91E3 |
SHA-256 | 5B9B743733EB5A18CEAE4AB370FC2C176DF496ACD07AF0E0622E68DCCF485E74 |
SHA-512 | AEB85CAFD5BA54630F79178CAD20CB476C835EA11619404F8221E8525039EFE23539C5F14268A5707725AD1552D3719C0E73FE44C61F38E36F16B9F55A5B1010 |
SSDEEP | 192:KbsenKlgmgZS7y5u8GcTGILKZlV8CySH6uX:KjK+mHelBKZlOxSauX |
TLSH | T19FF1B563E94A6D6AAB13912E7607E053A32C2957625C5B38B8BE402C3F125B5C1F3DE4 |
insert-timestamp | 1640473768.2388349 |
mimetype | text/plain |
source | snap:GTna8U3HAhjvYZGcbeLR7V9U1EOGd139_24 |
tar:gname | root |
tar:uname | root |
hashlookup:parent-total | 13 |
hashlookup:trust | 100 |
The searched file hash is included in 13 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileName | http://archlinux.mirror.root.lu//pool//community//./python-smmap-1:3.0.4-3-any.pkg.tar.zst |
MD5 | E923A4FA33A74B76C68F71670CED4B9B |
SHA-1 | 621DED048679A673510A45A0CA87BD3B99396A92 |
SHA-256 | 4D04BCA755C853F51FC832988D7176C973DF829EA5AD579B2D2E8C8DD679B157 |
SSDEEP | 768:wE8MMQyLD7mdiD2kD6tfp/1TOZeLknO/jGhC0Qou+E:wBidiDZ6fbTXLn/AQo+ |
TLSH | T16403F19735BD3CF162F321B91CAD726A8190B2F762BA51E41FD80C90DB29563E904D2E |
Key | Value |
---|---|
MD5 | 326882D74DB979F3BCAC26F12854356D |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-smmap |
PackageRelease | bp153.1.15 |
PackageVersion | 3.0.2 |
SHA-1 | C30FADC8F99587782B70486D90A35A59EDDFADFC |
SHA-256 | CD7DBC70851E6DD8845359DE8F5E8AD89268DED86AD6BE26BDE97AB805FACD9C |
Key | Value |
---|---|
MD5 | D9DF19229FD05F9CF390A917F32CCECC |
PackageArch | noarch |
PackageDescription | MotivationWhen reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps.Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is... |
PackageMaintainer | guillomovitch <guillomovitch> |
PackageName | python3-smmap |
PackageRelease | 1.mga8 |
PackageVersion | 3.0.4 |
SHA-1 | B3A74BE178B76EB488A8EAA97F14B94C5FFECF60 |
SHA-256 | 161F04DCA080D0B06A1691DE97CD549006A72FFDD5B575956ED6210397ACD69F |
Key | Value |
---|---|
MD5 | 582609E66AE28FA3B8C4FDE3BEC69E20 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-smmap |
PackageRelease | lp152.1.1 |
PackageVersion | 3.0.2 |
SHA-1 | 8084D95FFDF84F8B5A595B640D1DCE7E58B888CD |
SHA-256 | E1A36F5A077F453CC657ECB6C62BCD5C2A045F8AC7940810A66C87DE645F1A29 |
Key | Value |
---|---|
MD5 | 633E49628825D678CFFF0BAFC2990FB5 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-smmap |
PackageRelease | bp154.1.49 |
PackageVersion | 3.0.2 |
SHA-1 | EFE2861D5538485CA5E6E6DFEFEC3826F5D80AC7 |
SHA-256 | 1AC3FADBAB590B94F96281D86619924FC99A9CFB21A9040CFB847C76125F83C6 |
Key | Value |
---|---|
MD5 | 21FA62F9049FA834951CA082AA085603 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python3-smmap |
PackageRelease | lp151.32.1 |
PackageVersion | 3.0.4 |
SHA-1 | C0148A9C2F9B74C4BBC2BA8B5ED0D93457662991 |
SHA-256 | 67B668796DB272ED99A663109AABD2CC8EB4F639F88BA429405B525E0B054AA7 |
Key | Value |
---|---|
FileSize | 21044 |
MD5 | F251647874CC2EE5ABF8E485F3F8BE2C |
PackageDescription | pure Python implementation of a sliding window memory map manager Smmap wraps an interface around mmap and tracks the mapped files as well as the amount of clients who use it. If the system runs out of resources, or if a memory limit is reached, it will automatically unload unused maps to allow continued operation. . This package for Python 3. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python3-smmap |
PackageSection | python |
PackageVersion | 3.0.4-1 |
SHA-1 | C41854A854D38C44675BD0EAD881C805C5745C95 |
SHA-256 | EFD7B71254D933762F68B488978B8CC6A29B080841EE4E81EAAB21BD303D24AE |
Key | Value |
---|---|
MD5 | BFDD21D520737E980D12B6BDE74EEAAA |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-smmap |
PackageRelease | lp152.1.1 |
PackageVersion | 3.0.2 |
SHA-1 | 574C5F92E3DA9AB72420A5AC366D1EB4F1C21481 |
SHA-256 | C41E1F11D6F8D083AEF35EF84481DBBF0B61BED3792019D2EF8A9EFA355596E6 |
Key | Value |
---|---|
SHA-1 | 6A1037D40822ED716807785E61844FFE1171E108 |
snap-authority | canonical |
snap-filename | GTna8U3HAhjvYZGcbeLR7V9U1EOGd139_24.snap |
snap-id | GTna8U3HAhjvYZGcbeLR7V9U1EOGd139_24 |
snap-name | bandit |
snap-publisher-id | f5QKIl96cy3xJ3iK1p6F4NNTwjCqAby8 |
snap-signkey | BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul |
snap-timestamp | 2020-01-30T17:01:54.680453Z |
source-url | https://api.snapcraft.io/api/v1/snaps/download/GTna8U3HAhjvYZGcbeLR7V9U1EOGd139_24.snap |
Key | Value |
---|---|
MD5 | 9A810B7873D0F518EBAD3C9CF8F9B695 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python3-smmap |
PackageRelease | 2.2 |
PackageVersion | 3.0.2 |
SHA-1 | 7DC1FE7856709ACFB815295162BDF95EFDA8F705 |
SHA-256 | 716395FD5EB9B82B93BF83842B9340179600EE9EC505E8455341F59B2B1D09B6 |
Key | Value |
---|---|
MD5 | A60FD260480F1786BA7B4F70DE9B9103 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-smmap |
PackageRelease | bp153.1.15 |
PackageVersion | 3.0.2 |
SHA-1 | CCEFBE7C48AB679E85AA799CBAA036350989747D |
SHA-256 | 243149CD67BC54E129F5D1ACB02EAAF848E8394F7511D23E29E4C96DC7408211 |
Key | Value |
---|---|
MD5 | 88CDA23F1EBD7BEC29713FD71ED90D6B |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageName | python2-smmap |
PackageRelease | lp151.32.1 |
PackageVersion | 3.0.4 |
SHA-1 | 4E980E0B878B3D516AEB5F5AFEE33D74F4FB6E5A |
SHA-256 | 1D4CC674807FB4410D51E7AF739A54E492A5F1A66E7EE26DDA4DFE898BBD32DA |
Key | Value |
---|---|
MD5 | FB6EB199BA1A89D1AD19F60D527835D8 |
PackageArch | noarch |
PackageDescription | When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps. Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. The documentation can be found here: http://packages.python.org/smmap |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-smmap |
PackageRelease | bp155.2.13 |
PackageVersion | 3.0.2 |
SHA-1 | 62B98D8C5C7D45FCAD152674114336FC030E8194 |
SHA-256 | A0AE96A6E2E7720FB3CE16305593EC4E5292A7824199BB0713C4351FCC9DD600 |