similar to: Single-instance storage Thank You

Below is the string to parse and return the embedded number = "11" string = "\t\t\t\t\t<span class=\"compliment-count profile\">11</span>" On Jul 29, 2012, at 3:00 AM, r-help-request@r-project.org wrote: > char [[alternative HTML version deleted]]

What options are available for remote storage, i.e. storage devices directly mounted on the machine running Dovecot? I've seen discussions of NFS usage - but my experiences with NFS in times past have been poor. CIFS has worked well for me for non-mail use - would this be suitable? Or is there another method I've not considered? -- Daniel

Dear All: stepping in late, but @Joris, if you would like to take 'from a single file' literally, have a look at: https://github.com/bpfaff/lp4rp (lp4rp: literate programming for R packages); Cheers, Bernhard ps: incidentally, within the noweb-file roxygen is employed. -----Urspr?ngliche Nachricht----- Von: R-devel [mailto:r-devel-bounces at r-project.org] Im Auftrag von Joris

I fully agree with Joris and Hadley on roxygen2. Additionally: I wrote and published my first package before roxygen (or roxygen2) was available. I found editing .Rd extremely terse (especially when code is updated). For example, the fact that there are no spaces allowed between } and { in \param{}{} has hurt my brain quite a few times, especially since R CMD check did not give any useful error

First, I compliment you all for such a useful project as R. Suggestion: If read.table() could take input from a character string, then one could write raw= " x y z 1 2 3 4 5 6 " df = read.table(raw,head=TRUE) Of course, one can cat() to write raw into a temporary file, and read.table() from that file. However, direct reading might be a good option? Hope this is

Below is a fix for the current problem of checksum offload not working in a NAT''ed network. The cause is the NAT/iptables code incorrectly modifying the TCP/UDP checksum (for the checksum offload case). The original code assumes a valid checksum, which is not the case for checksum offload packets (which has a complimented, partial checksum for the hardware to use). The fix is to

Am 2015-04-02 um 17:49 schrieb Reindl Harald: > Am 02.04.2015 um 14:30 schrieb Edwardo Garcia: >> On 4/1/15, Reindl Harald <h.reindl at thelounge.net> wrote: >>> Am 01.04.2015 um 14:33 schrieb Bernd Petrovitsch: >>>> On Mit, 2015-04-01 at 13:07 +0200, Reindl Harald wrote: >>>>> Am 01.04.2015 um 13:04 schrieb Bernd Petrovitsch: >>>>>

On 31/01/2018 6:33 AM, Joris Meys wrote: > 3. given your criticism, I'd like your opinion on where I can improve > the documentation of https://github.com/CenterForStatistics-UGent/pim. > I'm currently busy updating the help files for a next release on CRAN, > so your input is more than welcome. After this invitation I sent some private comments to Joris. I would say his

I have read most of the doc on the dovecot website, and couldn't find any info on the single instance storage feature, so I'm posting my questions here. - Are these 3 parameters the only one necessary for single instance storage? I cannot find any doc on this feature on the website; is there anything specific I need to know about them? (the last one isn't exactly self-explanatory). -

On 12/2/2007, Timo Sirainen (tss at iki.fi) wrote: > On Sun, 2007-12-02 at 10:02 -0500, Charles Marcus wrote: >> Do you have any idea as to a time frame for when you might be able >> to get to it (Single instance Storage)? Are you thinking post >> v2.0? Even 2.1 or 3.0? > Right now I just want to get v1.1 finished. The main problem with it > is that apparently in

hi, I am currently experiencing a problem: there is a group of 200 people to this group when a user send a large message (50MB), can easily lead to congestion. Is there a good way to handle such a situation, like the hard link cyrus?

Does the "doveadm purge" operation delete unused attachments? -- Daniel

Ok, didn't find much on this... The bottom of /etc/dovecot/conf.d/10-mail.conf has the following settings: #mail_attachment_dir = #mail_attachment_min_size = 128k #mail_attachment_fs = sis posix #mail_attachment_hash = %{sha1} all of which are apparently the defaults according to doveconf -d output - so no need to set them explicitly, unless I want to change them, right? So, enable the

Hi everyone, I tried to find info about this online, but I couldn't find anything talking specifically about what I am trying to accomplish. I am sending and receiving the same attachments pretty often and as a result my email accounts are growing much more rapidly than I would like. *My goal* is to set up a second instance of Dovecot with SIS enabled and transfer everything over to this

Hey Timo, I was curious where Single Instance Storage fits in on the roadmap, now that you are maybe settled in in your new digs... Is it still coming soon? Has it been pushed back by your new employers priorities? Its real high on mine, so if has been back-burnered, I'll need to start looking for alternatives... Thanks, -- Best regards, Charles

Just a note to myself and whoever else cares, should be added to wiki once it has its own page about this: With single-dbox messages can be copied with hard linking. This means that there can be multiple files that point to the same attachment file. The attachment is now deleted only once the mail file's link count drops to zero, so this works fine.. ..until someone goes and starts manually

Most people (even Eniripsa players) see Eniripsa solely as support characters. They are support characters, but to limit an Eniripsa to purely support status, one never realises an Eniripsa's true power. Alot of guides will tell you that Eniripsa are "leech fairies" for most levels, that is not the case if built properly. The important thing to remember when building a solo Eniripsa

This single-instance storage is going to encourage bad habits! I just found myself preparing an e-mail that needs to be sent to multiple recipients - including several within my own organization - yet it's not necessary for everyone (in-house) to get the large attachment. As I was getting ready to split the message into two parts for distribution I remembered - I can just send it to

http://hg.dovecot.org/dovecot-2.0-sis contains the code for it. Otherwise it's the latest (as of writing this) dovecot-2.0 hg tree. Please test if you're interested in SIS. :) Once there's at least some testing, I'll probably add this to v2.0.x since very little of this new code is used when SIS is disabled (which is the default of course). SIS works pretty much like explained in

I'm running Dovecot 2.3.4 with Single Instance Storage (SIS) and zlib and I am frequently seeing errors where files are missing in the attachments directory even though the zipped file in the hash directory is actually there.? This appears not to have been an issue in Dovecot 2.3.1 Requested output of the server below. The error looks like this in the log Dec 18 08:58:58 dovecot01