similar to: feature request - zlib compression via LDA

Hello Dovecot v2.0.5 zlib_save_level = 6 # 1..9 zlib_save = gz # or bz2 Is there a config option to disable zlib, even if above config are in place? If so please provide an example. If no, would it be possible to add one? Like if zlib_save_level = 0 disable zlib. So one can configure per mailbox compression level via sql database. KuiZ Thanks

https://bugzilla.samba.org/show_bug.cgi?id=14390 Bug ID: 14390 Summary: Feature request: don't fail if using "-z" transferring to rsync complied with --with-included-zlib=no Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement

Hello OpenSSH developers, openssh 4.2p1 breaks old openssh clients up to 3.4p1 when they try to use compression: # ssh-3.4p1 -C remote-host-with-4.2p1 pwd no matching comp found: client zlib server none,zlib at openssh.com option "-vv" shows ... debug2: kex_parse_kexinit: zlib ... debug2: kex_parse_kexinit: none,zlib at openssh.com ... debug2: mac_init: found hmac-md5 no

Folks, I'd like to get expert's opinion on which compression level is suitable for lld's -compress-debug-section=zlib option, which let the linker compress .debug_* sections using zlib. Currently, lld uses compression level 9 which produces the smallest output in exchange for a longer link time. My question is, is this what people actually want? We didn't consciously choose

Hello, I'm one of the Debian maintainers of rsync and I'm currently investigating the switch from "--with-included-zlib=yes" to "no" for the next stable release (ETA 2021). So basically I'm investigating what are the impacts of using upstream's zlib instead of rsync's bundled one. For the investigation I did simple transfers (1 file) using both

Also not an expert, but would it make sense for this to be configurable at a fine-grained level, perhaps with another option, or an extension to the compress-debug-sections switch interface? That way users who care about the finer details can configure it themselves. And we should pick sensible options for the default. James On 2 August 2018 at 11:08, Pavel Labath via llvm-dev < llvm-dev at

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u

Hi Rui, What's the intended advantage for compressing the debug sections? - (i) Improved link time through smaller IO / (ii) Improved Load / startup time for the debugger / (iii) Smaller exe with debug info for distribution / disk space? For i) and ii) how much this is worth it depends on balance of storage bandwidth to compression (i) / decompression (ii) bandwidth. For spinning drives it

> As to (3), in most cases, I believe it is rare to distribute executables with debug info widely > I think it is at least less important than (1). Agreed. > I think (1) is definitely the case, and that's also true for a distributed build system with which a lot of object files are copied between machines. > My suggestion was to use compression level 9 when both -O2 and

> On 10/11/2020 20:07 Daniel Sch?tze <dms at cwa.uk.com> wrote: > > > Dear Aki > Thank you. Unfortunately I'm struggling to get the right syntax for this as it looks like someone else was here too > https://dovecot.org/pipermail/dovecot/2018-July/112441.html > The location in my dovecot.conf is > >

Hi! I've followed the guide at http://wiki2.dovecot.org/Plugins/Zlib to try to make Dovecot gzip incomming mails, but it doesn't seem to work. I've made pop/imap read gzipped files, and this seems to work perfectly, but LDA is still saving incomming mails in plain text. There's not too much information out there regarding the zlib module, so I'm not sure where to start

Not really, as well as some sensitivity to the input data overall performance of the link with compression will depend on how this is implemented in lld - how is it parallelized? How is it chunked? Is it effectively pipelined with IO? Or, I wouldn't feel comfortable being able to make a recommendation to our end-users on whether to use this option or not based on my existing extensive

Hi, I'm wondering if someone already implemented a compression script (and would like to share it) based on the step-by-step provided on wiki page of Zlib module. I can already do some find|xargs gzip .... but couldnt implement it completly as described on the wiki page. I know the suggested step-by-step is very detailed and probably a must simplier will be enough for almost

Hello, I use mbox compressed by gzip as read-only folder (using zlib plugin). I have errors in logs: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) and can't read messages in MUA. IMAP commands to reproduce a bug: 1 SELECT "compressed.gz" 2 UID fetch 2 BODY.PEEK[] # sleep 5 3 UID fetch 2 BODY.PEEK[] # repeat sleep/fetch until assert (a

On 07/05/17 13:25, Aki Tuomi wrote: >> I use mbox compressed by gzip as read-only folder (using zlib plugin). >> >> I have errors in logs: >> Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion >> failed: (ret == -1) ... >> The bug appeared in 2.2.26 and still can be reproduced (in 2.2.31) >> >> Using 'git bisect' was not

Attached is a zlib advisory and a debug dump of ssh with compression enabled. Most of the debug is superflous, so I have underlined the two points to look at. When creating an ssh connection, compression on the line is done *before* authentication -- This means an unauthorized attacker could, conceivable, leverage root access by connecting with to the ssh server requesting zlib compression and

http://bugzilla.mindrot.org/show_bug.cgi?id=788 Summary: request for zlib.h configure test Product: Portable OpenSSH Version: -current Platform: PPC OS/Version: AIX Status: NEW Severity: enhancement Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy:

Dear All, I think I am confused about how I'd be able to use zlib starting with R 2.7.0. I just downloaded the latest development version, built it, etc, but I am not able to find the zlib.h that, I believe, R should place somewhere under "where/you/want/R/to/go" (from --prefix=/where/you/want/R/to/go). There seem to be entry points for zlib in the binary (e.g., grep -r gzopen ./

Hello, is it possible to compress by zlib only selected folders? My e-mail accounts have archive folder and this folder contains old comunications with my customers and this I use very rare, so I want to compress them by zlib to save space. Is this possible? Thanks, Filip Bartmann

Hello, many linux SW is starting to implement new lzma compresson instrad of old zlib (gzip) od bzip2. lzma is default comrpession in very good compression SW 7-zip, which is faster and have higher compression ratio then bzip2 or rar. Currently its probalby the best compressor in therms of compression and decompression speed / compression ratio. In linux there is GNU lzma SW which implements