search for: port_

Greetings, thanks to all of you who work on Dovecot! I have prepared a small patch to support Solaris 10 and Opensolaris' event port mechanism for both the ioloop and the notify subsystems. It seems to work fine for me, but I haven't conducted any extensive testing. It would be great if someone could review and/or test it (and if it could eventually enter the code base). I have

Hello. I am trying to save an object which I created using assign as following: assign(paste(NombreAlgoritmo,"_Portafolio",sep=""),PortafolioInicial) save(get(paste(Algoritmo,"_Portafolio",sep="")),file=paste(camino,"\\Libreria\\Portafolio\\Port_",NombreAlgoritmo,"\\",NombreAlgoritmo,"_Portafolio.Rdata",sep="")) but I am getting the following error: Error in save(get(paste(NombreAlgoritmo, "_Portafolio", sep = "")), file = paste(camino, : object 'get(paste(NombreAlgoritmo, &quot...

...++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c > index 6bf0df3..a39702a 100644 > --- a/drivers/char/virtio_console.c > +++ b/drivers/char/virtio_console.c > @@ -749,6 +749,10 @@ static ssize_t port_fops_read(struct file *filp, char __user *ubuf, > > port = filp->private_data; > > + /* Port is hot-unplugged. */ > + if (!port->guest_connected) > + return -ENODEV; > + What if the port is hot-unplugged after this check? Should we serialize the hot plug with inbuf...

...++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c > index 6bf0df3..a39702a 100644 > --- a/drivers/char/virtio_console.c > +++ b/drivers/char/virtio_console.c > @@ -749,6 +749,10 @@ static ssize_t port_fops_read(struct file *filp, char __user *ubuf, > > port = filp->private_data; > > + /* Port is hot-unplugged. */ > + if (!port->guest_connected) > + return -ENODEV; > + What if the port is hot-unplugged after this check? Should we serialize the hot plug with inbuf...

...listeners and then use CoS setup with multiple passdb:s. something like: service imap-login { inet_listener imap { port = 143 } inet_listener imap2 { port = 144 } } and then in first passdb fetch configuration variables: passdb { driver = passwd-file args = username_format=port_%{lport} /etc/dovecot/extrasettings.passwd result_failure = continue result_internalfail = continue result_success = continue } passdb { ?. } and in second passdb {} you can use %{passdb:variables} that you set in the first passdb. Probably can?t set driver = %{passdb:driver} tough.. maybe...

...sertions(+), 1 deletion(-) > > > > diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c > > index 6bf0df3..a39702a 100644 > > --- a/drivers/char/virtio_console.c > > +++ b/drivers/char/virtio_console.c > > @@ -749,6 +749,10 @@ static ssize_t port_fops_read(struct file *filp, char __user *ubuf, > > > > port = filp->private_data; > > > > + /* Port is hot-unplugged. */ > > + if (!port->guest_connected) > > + return -ENODEV; > > + > > What if the port is hot-unplugged after this check...

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver =