similar to: Corrupted indices (and accidental checkin)

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

Hey, There are some patches I''ve and a bunch of other work that I forsee coming that will mean more patches. I was wondering what the process is of getting checkin access for the Xen tree? P.S. ''konradwilk'' is the account name.

Checkin 1.37 of src/lib-storage/mail-storage.c added a parameter to mailbox_open() but this broke building src/deliver/deliver.c as revision 1.2 doesn't use the new parameter. It looks like save_mail() of src/deliver/deliver.c calls mailbox_open() and it looks like it might work fine if it were to use a (struct istream *)0 as the third parameter (instead of the flags) -- but I don't use

Hi I would like to ask how to configure the email address that will email to me and to the person who has checked in the files that has broken the build. //Currently the email is fixed in the configfile with me as the sole address project.email_notifier.emails = [''me at myemailaddress.com''] Does anybody know how to change the email address dynamically following a build fail

Hi, When I run RCMD check on my package, I receive the following error: C:\R-packages\AnnotationFuncs>RCMD check --no-vignettes AnnotationFuncs * using log directory 'C:/R-packages/AnnotationFuncs/AnnotationFuncs.Rcheck' * using R version 2.13.0 (2011-04-13) * using platform: i386-pc-mingw32 (32-bit) * using session charset: ISO8859-1 * using option '--no-vignettes' * checking

This is the trace (gdb) run Starting program: /root/tmp/dovecot-1.0.rc7/src/imap/imap x select inbox Program received signal SIGSEGV, Segmentation fault. mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at mail-index.c:1313 1313 memcpy(index->map->mmap_base, hdr, hdr_size); (gdb) bt #0 mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at

When setting a CONTROL directory that does not exists (has to be created by dovecot upon first login) AND INDEX=MEMORY Dovecot POP3 will fail upon first login with 'Couldn't init INBOX: Internal error occurred. Refer to server log for more information.' Temporary fix seems to work fine patching dovecot-1.1.16/src/lib-storage/index/maildir/maildir-util.c ---- 98a99

I know people who shutdown the services on their *nix box before backing up with rsync. this is to avoid accidentily backing up files that are being written to, which might result in a corrupt backup of that file. is this even a concern? if it is, what methods are available for a small shop to schedule regular backups but still maintain uptime? thanks!

Is there any way to obtain the public key from the private key? I know it's in host file however for the purpose of this message I need to be able to generate it on the command line. I tried openssl ec < ed25519_key.priv I get an error read EC key unable to load Key 140092556813984:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:703:Expecting: ANY PRIVATE KEY

Hello list, Thanks in advance for any help. I have many (approx 20) files that I have merged. For example d1<-read.csv("AlleleReport.csv") d2<-read.csv("AlleleReport.csv") m1 <- merge(d1, d2, by = c("IND", intersect(colnames(d1), colnames(d2))), all = TRUE) m2 <- merge(m1, d3, by = c("IND", intersect(colnames(m1), colnames(d3))), all =

I accidentally created a controller with the wrong name. Obviously I don''t want to have this useless controller hanging around - is there a prescribed way to delete the controller or can I just delete the controller file? -- Posted via http://www.ruby-forum.com/.

Hi all, Does anyone know if it's possible to recover an LVM partition from a drive that was fdisked? I accidently fdisk'd the wrong drive (had to fdisk a lot of 160GB drivers from old servers and one still has important data on that client now wants) by running fdisk /dev/sdc & deleting the partitions. The drive is still in a another machine and hasn't been rebooted yet, but

On Sun, Mar 7, 2010 at 8:50 AM, nate <centos at linuxpowered.net> wrote: > > re-create the original partition table, which is just a map, as long > as you haven't formatted or overwritten data everything should still > be there > > Also suggest if your not already doing it set your LVm partitons to > type 8e so it's obvious they are LVM > > [root at

This bug was reported to Debian but I feel it is an upstream issue. On Sat, 4 Jan 2003, Amelia A Lewis wrote: > If dovecot is misconfigured, such that imap-auth cannot find passwd.imap > (which probably needs to get copied; maybe need more docco in the config > file? This happens if the digest-md5 auth method is uncommented and the > auth_userinfo is set to passwd-file

im betting here on a smb.conf that was not 4.6 compliant. port 49152 is not related i my opinion. is there a firewall running? the dynamic port range changed from a low range to high. Greetz Louis Op 17 mrt. 2019, om 22:36, Rowland Penny via samba <samba at lists.samba.org> schreef: On 17 Mar 2019 20:44:12 UTC Don Kuenz via samba <samba at lists.samba.org> wrote:

There is an rsync/popt/config.log in CVS - presumably an accidental "cvs add". Max.

https://reviews.llvm.org/rL353906 introduced (presumably accidentally) the "b" top-level directory to the monorepo. The files should be moved to their proper location, but I'm also wondering if there's any way to prevent accidental top-level additions like this. Thanks, Shoaib -------------- next part -------------- An HTML attachment was scrubbed... URL:

Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the

I know there is no straightforward way to recover deleted files on an ext3 file system, but is there any way to recover from an accidental mke2fs? -- --------------------------------------------------------------- Paul Raines email: raines@nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street tel:(617)-724-2369

I had a recent disaster scenario with rsync. I was wondering if there were any suggestions to guard against in the future: I used to maintain "mirror" backups of the /home dir on our production_server using rsync to a backup_server. The primary server had a rsyncd daemon running and the backup_server had this line in the crontab: 10 01 * * * rsync -av --delete root at