similar to: New version of UFO - is there a new HOWTO?

I was running the previous version of UFO, the 3.3 one that was based on Swift 1.4.8. Now there is a 3.3.1 based on Swift 1.7.4. The config that I used last time to enable S3 isn't working with the new one, just updated yesterday using yum. I was using tempauth in the old version and I'm still using tempauth. I have a CentOS 6 system and a Fedora 18 system with UFO on them. The

On 5/9/2018 10:15 PM, Shawn Heisey wrote: > It's been about three weeks since I asked this question.? All the > information I have available says that all users have no limits on > virtual memory, so it must be dovecot itself that sets the limit.? Can > that be changed in the 1.2 version?? I can't upgrade to 2.x yet. > > Here's an actual syslog entry, redacted to

I have an idea I'd like to run past everyone. Every gluster peer would have two NICs - one "public" and the other "private" with different IP subnets. The idea that I am proposing would be to have every gluster peer have all private peer addresses in /etc/hosts, but the public addresses would be in DNS. Clients would use DNS. The goal is to have all peer-to-peer

Hello Everyone, I am using Zabbix to monitor my Dovecot server, and my logs are filled with lines like this: > Oct 21 15:04:46 osaka dovecot[1256]: pop3-login: Aborted login (no auth > attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, > session=<bWd0nr14SuF/AAAB> > Oct 21 15:05:29 osaka dovecot[1256]: imap-login: Aborted login (no auth > attempts

On a new puppet master node I get this error on a puppet apply for an OpenStack multi-node setup. This is a new one I have never seen before. Tips? debug: Prefetching keystone resources for keystone_user err: Could not prefetch keystone_user provider ''keystone'': File: /etc/keystone/keystone.conf does not contain a section DEFAULT with the admin_token specified. Keystone

i use solr fts indexing. It worls very well but it have one database per system, not per user. Lets suppose i delete one or more e-mail users in system. How to remove them in solr database to reclaim space?

I have a machine with my mail service on it running Debian Squeeze. The version of dovecot on that server is 1.2.15. I'm building a new server with Ubuntu 18.04 (started with 16.04, upgraded in place), where the dovecot version is 2.2.33. I plan to migrate all my services to this new machine. The virtual mailboxes are on disk in maildir format, with accounts in a mysql database managed by

https://bugzilla.mindrot.org/show_bug.cgi?id=926 Jan Engelhardt <jengelh at gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh at gmx.de --- Comment #33 from Jan Engelhardt <jengelh at

Package: logcheck-database Version: 1.2.54 Severity: normal Tags: patch When views are used in bind, the logcheck filters don't catch the common informational log messages. Added regex bits to the filter definitions. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

https://bugzilla.samba.org/show_bug.cgi?id=10636 Summary: Feature request: Show current source path on receipt of Posix signal Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at

HI all, I''m trying to demo the puppetlabs-openstack module following the the simple example, but not getting very far. the puppetlabs-keystone module is presenting a weird failure state claiming: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type keystone_tenant at

I remember reading about post hoc statistical power on R-help. But I can't seem to find them with RSiteSearch("post hoc statistical power") and variations of it. I would like to learn more about post hoc statistical power, its meaningfulness, advantages and disadvantages. I thought the issue was settled after Tukey's 1993 paper about post hoc statistical power being

commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4 Author: Ben Hutchings <ben at decadent.org.uk> Date: Thu Oct 30 18:27:12 2014 +0000 drivers/net: Disable UFO through virtio Turned off UFO support to virtio-net based devices due to issues with IPv6 fragment id generation for UFO packets. The issue was that IPv6 UFO/GSO implementation expects the fragment id to be supplied in

commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4 Author: Ben Hutchings <ben at decadent.org.uk> Date: Thu Oct 30 18:27:12 2014 +0000 drivers/net: Disable UFO through virtio Turned off UFO support to virtio-net based devices due to issues with IPv6 fragment id generation for UFO packets. The issue was that IPv6 UFO/GSO implementation expects the fragment id to be supplied in

On 08/17/2016 09:56 AM, Kaleb S. KEITHLEY wrote: > I propose to present on one or more of the following topics: > > * NFS-Ganesha Architecture, Roadmap, and Status,Jiffin Thotton copresenter. > * Architecture of the High Availability Solution for Ganesha and Samba > - detailed walk through and demo of current implementation > - difference between the current and storhaug

Hello everyone, I would like to ask a question regarding to disable UFO of virtio vNIC in my guest. I have read the document at https://libvirt.org/formatdomain.html *host* The csum, gso, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off host offloading options. By default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU only)* The

IPv6 does not allow fragmentation by routers, so there is no fragmentation ID in the fixed header. UFO for IPv6 requires the ID to be passed separately, but there is no provision for this in the virtio net protocol. Until recently our software implementation of UFO/IPv6 generated a new ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet passed through a tap, which is even

IPv6 does not allow fragmentation by routers, so there is no fragmentation ID in the fixed header. UFO for IPv6 requires the ID to be passed separately, but there is no provision for this in the virtio net protocol. Until recently our software implementation of UFO/IPv6 generated a new ID, but this was a bug. Now we will use ID=0 for any UFO/IPv6 packet passed through a tap, which is even

On Wed, 2014-11-19 at 11:14 +0200, Michael S. Tsirkin wrote: > On Thu, Oct 30, 2014 at 06:27:12PM +0000, Ben Hutchings wrote: > > IPv6 does not allow fragmentation by routers, so there is no > > fragmentation ID in the fixed header. UFO for IPv6 requires the ID to > > be passed separately, but there is no provision for this in the virtio > > net protocol. > >

On Wed, 2014-11-19 at 11:14 +0200, Michael S. Tsirkin wrote: > On Thu, Oct 30, 2014 at 06:27:12PM +0000, Ben Hutchings wrote: > > IPv6 does not allow fragmentation by routers, so there is no > > fragmentation ID in the fixed header. UFO for IPv6 requires the ID to > > be passed separately, but there is no provision for this in the virtio > > net protocol. > >