similar to: add basic systemd support to dovecot

On 2017-05-08 16:23, Reuben Farrelly wrote: > > > On 8/05/2017 9:13 PM, Aki Tuomi wrote: >> >> >> On 2017-05-08 13:52, Reuben Farrelly wrote: >>> Hi, >>> >>> Following up on this as there has been no response and the problem >>> is still present. As this is the master-2.2 branch I would have >>> thought it would compile

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS nailbunny at localhost is unavailable: > Sorry to take a while to get back to you

On 05/25/2015 03:44 PM, Steve Litt wrote: > Hey guys, please tell me that Dovecot does not depend on systemd! > Nope, Dovecot doesn't depend on systemd. Why should it depend on systemd? But: Dovecot supports systemd. If you want to enable systemd, use: ./configure --with-systemdsystemunitdir Regards, Pascal -- The trapper recommends today: beeffeed.1514517 at localdomain.org

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

On 8 May 2017, at 17.14, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > >>>>> On 28/04/2017 7:27 PM, Reuben Farrelly wrote: >>>>>> This has been broken for the last few days: >>>>>> >>>>>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to

Hi list, I tried to build rpm based on dovecot-2.2.2-2.fc20.src.rpm on Centos 6.4 rpmbuild --define 'rhel 64' -ba dovecot-2.2.spec I get this error: checking for C compiler default output file name... configure: error: in `/home/builder/rpmbuild/BUILD/dovecot-2.2.2': configure: error: C compiler cannot create executables See `config.log' for more details. (config.log

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

Thanks Dan and Charles - I've found the usb passthrough will be a non-starter (not supported on my host). Dan - is your recommendation to build Nut from source or just the driver? I'm trying to build the whole project but am obviously missing dependencies... I've come across a configure error syntax error near unexpected token `CPPUNIT,' which I've seen in a previous

The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc:

On 21/02/2016 10:43 PM, aki.tuomi at dovecot.fi wrote: >> The PID-File seems to be expected under yet another sub-dir of >> /var/run/dovecot. >> >> Regards >> Thomas > > Hi, > > This is fixed in > https://github.com/dovecot/core/commit/22d75d47097ca83c6e824a5129d81e8f18fb589b > > --- > Aki Tuomi This doesn't seem to be fixed for me, with

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

Hi all, I am doing some final testing of the libusb-1.0 branch (specifically https://github.com/zykh/nut.git branch libusb-1.0+0.1 @ dfd514e7), and I am running across a regression in usbhid-ups relative to the previous libusb-0.1 code running on FreeBSD. Basically, the master (2.7.4+; c703fa75) code was able to start running as root, drop privileges (usually to uucp, the default for the ports

El 18/07/15 a les 17:03, Charles Lepple ha escrit: > On Jul 17, 2015, at 9:42 AM, dmanye <dmanye at urv.cat> wrote: > >> so i reinstalled again... but instead of using four separate partitions for /, /usr, /var and /tmp, put all the stuff under an unique / partition and... it works! why exactly? no idea, because if i'm not wrong, nut sensitive stuff is under /lib, /sbin,

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

Not sure if the issue is limited to the Debian Auto-Builds, but after the latest commits an update of the packages fails: https://github.com/dovecot/core/commit/53cc71cae88ee81fd7eae47aed743496f8c884a2 Feb 21 07:31:22 nihlus dovecot: master: Dovecot v2.2.devel (950a6e6) starting up for imap, lmtp Feb 21 07:31:22 nihlus systemd[1]: PID file /var/run/dovecot/dovecot/master.pid not readable (yet?)

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM:

Cleanup make system so that all noninstalled headers are put to noinst_HEADERS. This quarentees that header will be present in tar ball but not installed with make install. CC: nouveau at lists.freedesktop.org Signed-off-by: Pauli Nieminen <suokkos at gmail.com> --- Makefile.am | 6 +++--- intel/Makefile.am | 10 ++++++---- nouveau/Makefile.am | 4 +++- 3 files changed,

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

nut hardcodes systemdsystemshutdowndir to ${libdir}/systemd/system-shutdown. This is not valid: - Executable helpers are installed to ${libexecdir}, which is different from ${libdir} on bi-arch systems. - Even if nut will use ${libexecdir}, it could be different from systemd libexecdir. That is why it is better to check systemd.pc for the correct path. That path is stored as systemdutildir.