search for: mrst

Hello! I'm attempting to get Dovecot working with MySQL user database on another machine. I can connect to the MySQL (5.7.26) instance with SSL enabled: ?mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem --ssl-cert=/etc/dovecot/client-cert.pem --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA -u vmail -p However if I use the same values in dovecot-sql.conf.ext, I get the following error: Jul 19 00:20:18 turin dovecot: master: Dovecot v2.3.7...

On 18/07/2019 23:24, Reio Remma via dovecot wrote: > Hello! > > I'm attempting to get Dovecot working with MySQL user database on > another machine. I can connect to the MySQL (5.7.26) instance with SSL > enabled: > > ?mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem > --ssl-cert=/etc/dovecot/client-cert.pem > --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA > -u vmail -p > > However if I use the same values in dovecot-sql.conf.ext, I get the > following error: > > Jul 19 00:20:18 turi...

...ith MySQL user database on </div> <div> another machine. I can connect to the MySQL (5.7.26) instance with SSL </div> <div> enabled: </div> </blockquote> <blockquote type="cite"> <div> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem </div> <div> --ssl-cert=/etc/dovecot/client-cert.pem </div> <div> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA </div> <div> -u vmail -p </div> </blockq...

...e on </div> <div> another machine. I can connect to the MySQL (5.7.26) instance with SSL </div> <div> enabled: </div> </blockquote> <blockquote type="cite"> <div> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem </div> <div> --ssl-cert=/etc/dovecot/client-cert.pem </div> <div> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA </div> <div> -u vmail -p </di...

...9 0:24, Reio Remma via dovecot wrote: >>>>>> I'm attempting to get Dovecot working with MySQL user database on >>>>>> another machine. I can connect to the MySQL (5.7.26) instance with SSL >>>>>> enabled: >>>>>> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem >>>>>> --ssl-cert=/etc/dovecot/client-cert.pem >>>>>> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA >>>>>> -u vmail -p >>>>>> However if I use the same values in dovecot-s...

On 19.07.2019 0:24, Reio Remma via dovecot wrote: > I'm attempting to get Dovecot working with MySQL user database on > another machine. I can connect to the MySQL (5.7.26) instance with SSL > enabled: > > mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem > --ssl-cert=/etc/dovecot/client-cert.pem > --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA > -u vmail -p > > However if I use the same values in dovecot-sql.conf.ext, I get the > following error: > > Jul 19 00:20:18...

...; wrote: >> >> >> On 19.07.2019 0:24, Reio Remma via dovecot wrote: >>> I'm attempting to get Dovecot working with MySQL user database on >>> another machine. I can connect to the MySQL (5.7.26) instance with SSL >>> enabled: >>> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem >>> --ssl-cert=/etc/dovecot/client-cert.pem >>> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA >>> -u vmail -p >>> However if I use the same values in dovecot-sql.conf.ext, I get the >>> following er...

..., Reio Remma via dovecot wrote: >>>>> I'm attempting to get Dovecot working with MySQL user database on >>>>> another machine. I can connect to the MySQL (5.7.26) instance with >>>>> SSL >>>>> enabled: >>>>> mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem >>>>> --ssl-cert=/etc/dovecot/client-cert.pem >>>>> --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA >>>>> -u vmail -p >>>>> However if I use the same values in dovecot-sql.conf.ext, I g...

Hello Anton! > Some of the behavior seen there was for a purpose, > like the heuristics to overcome different problems. > I have to remember all the details :) I have read your article "Improving Switch Lowering for The LLVM Compiler System" and thought that the selection mechanism works out well; by chance however I found that this mechanism does not work as designed if

...b/drivers/gpu/drm/gma500/psb_intel_lvds.c index 483fdce74e39..0066fe7e622e 100644 --- a/drivers/gpu/drm/gma500/psb_intel_lvds.c +++ b/drivers/gpu/drm/gma500/psb_intel_lvds.c @@ -388,11 +388,11 @@ bool psb_intel_lvds_mode_fixup(struct drm_encoder *encoder, /* PSB requires the LVDS is on pipe B, MRST has only one pipe anyway */ if (!IS_MRST(dev) && gma_crtc->pipe == 0) { - printk(KERN_ERR "Can't support LVDS on pipe A\n"); + pr_err("Can't support LVDS on pipe A\n"); return false; } if (IS_MRST(dev) && gma_crtc->pipe != 0) { - printk(...

...intel_lvds.c > index 483fdce74e39..0066fe7e622e 100644 > --- a/drivers/gpu/drm/gma500/psb_intel_lvds.c > +++ b/drivers/gpu/drm/gma500/psb_intel_lvds.c > @@ -388,11 +388,11 @@ bool psb_intel_lvds_mode_fixup(struct drm_encoder *encoder, > > /* PSB requires the LVDS is on pipe B, MRST has only one pipe anyway */ > if (!IS_MRST(dev) && gma_crtc->pipe == 0) { > - printk(KERN_ERR "Can't support LVDS on pipe A\n"); > + pr_err("Can't support LVDS on pipe A\n"); > return false; > } > if (IS_MRST(dev) && gma_cr...

Joe Perches (2): drm: Use pr_cont where appropriate gpu: drm: Convert printk(KERN_<LEVEL> to pr_<level> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 3 +- drivers/gpu/drm/amd/amdgpu/amdgpu_afmt.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 4 +-

...b/drivers/gpu/drm/gma500/psb_intel_lvds.c index 483fdce74e39..0066fe7e622e 100644 --- a/drivers/gpu/drm/gma500/psb_intel_lvds.c +++ b/drivers/gpu/drm/gma500/psb_intel_lvds.c @@ -388,11 +388,11 @@ bool psb_intel_lvds_mode_fixup(struct drm_encoder *encoder, /* PSB requires the LVDS is on pipe B, MRST has only one pipe anyway */ if (!IS_MRST(dev) && gma_crtc->pipe == 0) { - printk(KERN_ERR "Can't support LVDS on pipe A\n"); + pr_err("Can't support LVDS on pipe A\n"); return false; } if (IS_MRST(dev) && gma_crtc->pipe != 0) { - printk(...