{"CRC32": "A03F5E19", "FileName": "./usr/share/doc/liblog-log4perl-perl/examples/l4p-tmpl", "FileSize": "1846", "MD5": "DD276FAD8DBCF912A0899229300140F8", "OpSystemCode": {"MfgCode": "1006", "OpSystemCode": "362", "OpSystemName": "TBD", "OpSystemVersion": "none"}, "ProductCode": {"ApplicationType": "Operating System", "Language": "Multilanguage", "MfgCode": "2500", "OpSystemCode": "51", "ProductCode": "163700", "ProductName": "Tails", "ProductVersion": "2.11"}, "SHA-1": "4570532DFF1FA80F85810DBBF0DBF2AB129EC4DA", "SHA-256": "DF417241E054E7DC68DB95FA341C1F76CDF5B97DC088EA767F0D2033F69749C5", "SSDEEP": "24:Tmq2amkaRpaIirvARnCRKy3hMMcXM5y9sN702ULDuBZMMM8cGJcvSm+bX+vvVmP5:KqakapnwvAZC2j/eg2suB1/b0p+762L", "SpecialCode": "", "TLSH": "T1CF319662140C2A74DF5F17DBC4C71864D634AA1D1D1FF4A2B0EE0B1D527DA40857A274", "db": "nsrl_modern_rds", "insert-timestamp": "1647004443.9908452", "source": "NSRL", "tar:gname": "root", "tar:uname": "root", "hashlookup:parent-total": 94, "parents": [{"FileName": "https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//powerpc//p5-Log-Log4perl-1.50.tgz", "MD5": "4D0085E82384101F7D8AC1D152D32D7E", "SHA-1": "004ABCA3831F367A1D19AC904A60F6A57E4BC19E", "SHA-256": "B5EA8757D585CB0BF30829F1250D3231BD7539881DAB270047F0D66A2445497E", "SSDEEP": "6144:ubmUNyJPBwqdzmkCwZ1FQn78UW07iruRw9rCXIw7:uKUNs5oY9q5Ly9rMx7", "TLSH": "T12B542393C7DBC719301A37BE53E537E3E98A495AC92A1E8DE0E88176B3904F752172D0"}, {"MD5": "92B71E64749905A7E018A03FD1D71886", "PackageArch": "noarch", "PackageDescription": "Log::Log4perl lets you remote-control and fine-tune the logging\nbehavior of your system from the outside. It implements the widely\npopular (Java-based) Log4j logging package in pure Perl.\n\nTo log into RRD database, install perl-Log-Log4perl-Appender-RRDs package.\nTo log into a database via DBI, install perl-Log-Log4perl-Appender-DBI package.\n\nTo read log4j XML configuration files, install\nperl-Log-Log4perl-Config-DOMConfigurator package.", "PackageMaintainer": "Fedora Project", "PackageName": "perl-Log-Log4perl", "PackageRelease": "1.el8", "PackageVersion": "1.50", "SHA-1": "00AC45EC737680D33C4B7954D645AD5D0AF237A1", "SHA-256": "6A9A4FAE38F2B276B6230D0CFF2F086394E3D83D7834E7643ABCE1C831E44E1A"}, {"FileName": "https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//sparc64//p5-Log-Log4perl-1.50.tgz", "MD5": "FD8AF546304E05227AD45BC17C20C23D", "SHA-1": "0154953A961170A37F7340D5BB919FBE83B98F3C", "SHA-256": "F3BE791D8980C6FB355C44FCE34003B143E661606F33CACF32DA53523090EC86", "SSDEEP": "6144:udbmUNyxPBwqdzmkCwZ1FQn78UW07iruRw9rCXIw7:udKUNc5oY9q5Ly9rMx7", "TLSH": "T1B4542393CBDBD325301637BE93E927E3ED49495A86262E9DE0F84132B3905F762172C1"}, {"MD5": "D9B0A3FB05052C02720C44DFAB4D1C0E", "PackageArch": "noarch", "PackageDescription": "Log::Log4perl lets you remote-control and fine-tune the logging behaviour\nof your system from the outside. It implements the widely popular\n(Java-based) Log4j logging package in pure Perl.\n\n*For a detailed tutorial on Log::Log4perl usage, please read*\n\nhttp://www.perl.com/pub/a/2002/09/11/log4perl.html\n\nLogging beats a debugger if you want to know what's going on in your code\nduring runtime. However, traditional logging packages are too static and\ngenerate a flood of log messages in your log files that won't help you.\n\n'Log::Log4perl' is different. It allows you to control the number of\nlogging messages generated at three different levels:\n\n  * At a central location in your system (either in a configuration file or in\nthe startup code) you specify _which components_ (classes, functions) of\nyour system should generate logs.\n\n  * You specify how detailed the logging of these components should be by\nspecifying logging _levels_.\n\n  * You also specify which so-called _appenders_ you want to feed your log\nmessages to (\"Print it to the screen and also append it to /tmp/my.log\")\nand which format (\"Write the date first, then the file name and line\nnumber, and then the log message\") they should be in.\n\nThis is a very powerful and flexible mechanism. You can turn on and off\nyour logs at any time, specify the level of detail and make that dependent\non the subsystem that's currently executed.\n\nLet me give you an example: You might find out that your system has a\nproblem in the 'MySystem::Helpers::ScanDir' component. Turning on detailed\ndebugging logs all over the system would generate a flood of useless log\nmessages and bog your system down beyond recognition. With 'Log::Log4perl',\nhowever, you can tell the system: \"Continue to log only severe errors to\nthe log file. Open a second log file, turn on full debug logs in the\n'MySystem::Helpers::ScanDir' component and dump all messages originating\nfrom there into the new log file\". And all this is possible by just\nchanging the parameters in a configuration file, which your system can\nre-read even while it's running!", "PackageName": "perl-Log-Log4perl", "PackageRelease": "lp151.40.1", "PackageVersion": "1.54", "SHA-1": "015EA738D0F85541D7B4DFC5E75734945F25EAA6", "SHA-256": "21728CC3B5740B352489A06E73D6FC621886447D481F52FA16EB752E1F2E3241"}, {"FileName": "http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//loongarch64//perl-log-log4perl-1.57-r1.apk", "MD5": "996E00D418B90999A5318E1F7FF9BB5A", "SHA-1": "02097CA435565FFE7F2FD00E7EDAAE52CE40A79E", "SHA-256": "38CC948B2D25E5ED1C339F47C7AE08B8F1861483E11F270FC39F26290238E2AA", "SSDEEP": "3072:vAJzqkJs6e1brF8iKmFIeDl/EmQuKVf07nyUP/P6Kqy5mHyKwTSERmwR:vAJPJsTqpaDjQ27nBPqty5WyKwAy", "TLSH": "T14DF312F154843FCAE97E641F0A47DDF68F3D8ADD095862A50E3E2864C4B861FB836581"}, {"FileName": "http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//armhf//perl-log-log4perl-1.57-r1.apk", "MD5": "13B1A1F4556FFFF516CDC75FB880DA93", "SHA-1": "03043A7C4AF345C51C08B80C1B13B59FC8995958", "SHA-256": "7C1C24F7B62F4D20D0BE56B88486B349EC08D5F87B4184D37D14BD2FE902F2EE", "SSDEEP": "3072:uYpHJdziUKpymXLI0Pga6UliJiPDQ6d4uWpP1UsRgCr7KbQUNJEfA+Gn:ttizpNLI0PgaVoice4bt1UUgUmE4JEy", "TLSH": "T1A9F312640958FA5F3C35ECEF5AF6C5E27A4BE6442AA8F03F8E5B6603D05342D1227487"}, {"FileName": "http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//s390x//perl-log-log4perl-1.57-r0.apk", "MD5": "369BC4A1048B036054F27B4356651D20", "SHA-1": "03081FA3FDC94321CBC1A60C2C4930978E6CF634", "SHA-256": "74785E067EF1F2B3E3E616DC38DCF147F7D8689E82BAB8CA22B951C1B00CFBBA", "SSDEEP": "3072:4n4ahpiwwTVDlpymkA1hfE6Uli0fImqUGlAg/9oOCCn4ekt0BteuodEGC8ix:44ah0DpyMhfEVqlqGGOCq4jt0BtdouGg", "TLSH": "T1FFF323D23D8A76B9880AF11F71DD03F1695875900635F077AAD8B663EA370E00297BDE"}, {"MD5": "5DD6EC80D79758B6C313D39860F54694", "PackageArch": "noarch", "PackageDescription": "Log::Log4perl lets you remote-control and fine-tune the logging behaviour\nof your system from the outside. It implements the widely popular\n(Java-based) Log4j logging package in pure Perl.\n\n*For a detailed tutorial on Log::Log4perl usage, please read*\n\nhttp://www.perl.com/pub/a/2002/09/11/log4perl.html\n\nLogging beats a debugger if you want to know what's going on in your code\nduring runtime. However, traditional logging packages are too static and\ngenerate a flood of log messages in your log files that won't help you.\n\n'Log::Log4perl' is different. It allows you to control the number of\nlogging messages generated at three different levels:\n\n  * At a central location in your system (either in a configuration file or in\nthe startup code) you specify _which components_ (classes, functions) of\nyour system should generate logs.\n\n  * You specify how detailed the logging of these components should be by\nspecifying logging _levels_.\n\n  * You also specify which so-called _appenders_ you want to feed your log\nmessages to (\"Print it to the screen and also append it to /tmp/my.log\")\nand which format (\"Write the date first, then the file name and line\nnumber, and then the log message\") they should be in.\n\nThis is a very powerful and flexible mechanism. You can turn on and off\nyour logs at any time, specify the level of detail and make that dependent\non the subsystem that's currently executed.\n\nLet me give you an example: You might find out that your system has a\nproblem in the 'MySystem::Helpers::ScanDir' component. Turning on detailed\ndebugging logs all over the system would generate a flood of useless log\nmessages and bog your system down beyond recognition. With 'Log::Log4perl',\nhowever, you can tell the system: \"Continue to log only severe errors to\nthe log file. Open a second log file, turn on full debug logs in the\n'MySystem::Helpers::ScanDir' component and dump all messages originating\nfrom there into the new log file\". And all this is possible by just\nchanging the parameters in a configuration file, which your system can\nre-read even while it's running!", "PackageName": "perl-Log-Log4perl", "PackageRelease": "1.2", "PackageVersion": "1.54", "SHA-1": "045A1256119349C964EB5014D924B6F8D499EA57", "SHA-256": "B2E51336223C24AFF4021B3832E192D61116375C8341A30A16AED76FBF7C100D"}, {"FileName": "https://ftp.lysator.liu.se/pub/OpenBSD/6.8/packages//sparc64//p5-Log-Log4perl-1.50.tgz", "MD5": "2E7F8B41985A5971DEFB021ADAE3884F", "SHA-1": "0616937820761A3CF1C72B43915B00E289AA6B9F", "SHA-256": "854107B2B93D6EEE6A097A7FE87994DF12185BFDAA3CBE5BB147976181BBAC9A", "SSDEEP": "6144:wLdbmUNyNPBwqdzmkiq8JUTccLX4kYa7XGWI6F:KKUN85ow8JUglkhWWI6", "TLSH": "T12D5423828DFD857EBD39B96142A349F3EFFF5B0461102C4CB0AD4A07795999623076E3"}, {"FileName": "https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//arm//p5-Log-Log4perl-1.50.tgz", "MD5": "61C8491FDBACA3F2BB2098E7C9459260", "SHA-1": "097B9DE77508A12E580C5127AC3C07A1EB51F4C8", "SHA-256": "D250A4007088B61CD8AFE75D8C730D8684FAA293EEFE530DAC2E1D8482903ED1", "SSDEEP": "6144:O+HIYGFofPBwqdzmkCwZ1FQn78UW07iruRw9rCXIw7:O+Hrh5oY9q5Ly9rMx7", "TLSH": "T1CB5423C3D2DB8311346A377F617823F3C5874D4A8AA51BD991E9C16A73E0CE253B61E4"}], "hashlookup:trust": 100}