similar to: dovecot and systemd

Hi, you've probably heard about systemd already. In Fedora 15, it's used as default instead old SysV init system. While there is some backward compatibility layer, everything is going to be ported from /etc/init.d/<something> init scripts to systemd's service files /lib/systemd/system/<something>.service Unfortunately?, systemd is not 1:1 compatible with old init

Hi Michal, I'm finally back on systemd integration with NUT. I've cc'ed Stanislav, since I've heard Suse is moving to systemd too. I've been investigation on your systemd integration in the tree, found a strange integration and understood why. I've fixed this with 2 commits: - r3528: only generate .in from configure, thus removing this annoying autoreconf msg - r3529:

On Wed, 14 Aug 2013, Michal Hlavinka wrote: >> The service unit consists of a new file >> /etc/systemd/system/ups-delayed-shutdown.service > > What exactly is this supposed to do? The proposed service unit fixes an openSUSE 12.3 problem, in which the UPS is not powered off on system shutdown. > When system is shutting down because of power failure (and low battery) >

On 08/10/2013 11:43 PM, Roger Price wrote: > OpenSUSE 12.3 has fully embraced systemd, but to get NUT working > correctly now requires some further systemd engineering in addition to > the usual NUT configuration files. A new systemd service unit is needed > to power off the UPS. > > The service unit consists of a new file > /etc/systemd/system/ups-delayed-shutdown.service

OpenSUSE 12.3 has fully embraced systemd, but to get NUT working correctly now requires some further systemd engineering in addition to the usual NUT configuration files. A new systemd service unit is needed to power off the UPS. The service unit consists of a new file /etc/systemd/system/ups-delayed-shutdown.service [Unit] Description=Initiate delayed UPS shutdown

Hi, thanks for the answer. I think your environment was not set up correctly to reproduce this bug. I've retested with 2.3.5 and I can still reproduce it. I've attached a script that will configure everything for testing and if you have a virtual machine available, you can use it directly (it expects linux with systemd for dovecot restart). relevant section from config: namespace {

Hi, we were modifying old SELinux rules for dovecot 2.0. Everything seems ok, only one report seems odd: "SELinux is preventing /usr/sbin/dovecot "write" access on dovecot.conf." Looking at strace output, dovecot tries to use socket on /etc/dovecot/dovecot.conf which is regular file and no socket: ... geteuid() = 0 getegid()

Sorry, we have not yet been able to look into this.. It's now in our internal system as DOP-966 Aki > On 7 March 2019 17:31 Michal Hlavinka via dovecot <dovecot at dovecot.org> wrote: > > > Hi, > any progress with this issue? Do you need more information to debug and > fix this? > > Cheers > Michal Hlavinka > > On 9/18/18 4:10 PM, Michal Hlavinka

Hi tl;dr: Seems that for Global ACL directory, namespace prefix is not part of the path, when looking for acl file. Long version: We're planning to update dovecot in next os update to 2.2.36 and while going through regression testing, we found a problem with ACL configuration combined with namespace. Test uses "Global ACL directory" configuration. Relevant configuration part:

Hello CentOS List, I have a server that has SysV script supplied by a hardware manufacturer, which is not functioning properly. From my reading, systemd-sysv-generator should handle them (like it did for Dell OpenManage software which supplied SysV init scripts). /usr/lib/systemd/system-generators/systemd-sysv-generator Takes no or 3 arguments (it tells me), but I didn't find clear

On Wednesday, 3 August 2016 16:39:46 CEST Richard W.M. Jones wrote: > On Wed, Aug 03, 2016 at 05:35:14PM +0200, Pino Toscano wrote: > > Currently we install a systemd service named firstboot.service and a > > SysV service named virt-sysprep-firstboot. On systems where systemd is > > the init system and runs with the SysV compatibility, the different > > names make

Currently we install a systemd service named firstboot.service and a SysV service named virt-sysprep-firstboot. On systems where systemd is the init system and runs with the SysV compatibility, the different names make systemd handle them as different services, and thus trying to run the firstboot script runner twice. Rename the systemd service to virt-sysprep-firstboot as well: other than being

Hi, we've seen SELinux reports from our users that dovecot tried to use something that needs CAP_NET_ADMIN capability. Before enabling it, we would like to know where it originated from. I've checked the sources, but was not able to find anything that would require this capability. Do you know for what it is used? CAP_NET_ADMIN Perform various network-related operations: * interface

On 4/12/19 12:48 AM, Stephan Bosch wrote: > > > On 29/03/2019 10:23, Michal Hlavinka via dovecot wrote: >> On 3/28/19 6:41 PM, Aki Tuomi via dovecot wrote: >>> >>>> On 28 March 2019 19:40 Michal Hlavinka via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> >>>> ? Hi, >>>> >>>> when trying to

Hi, yesterday lib-sql got driver-sqlpool with some changes in Makefile.am, but these changes in makefile works only for --with-sql=yes. When --with-sql=plugin is used build fails with: libtool --tag=CC --mode=link gcc -std=gnu99 -O2 -g -pipe -Wall -Wp,- D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 - m64 -mtune=generic -Wall -W -Wmissing-prototypes

On 3/28/19 6:41 PM, Aki Tuomi via dovecot wrote: > >> On 28 March 2019 19:40 Michal Hlavinka via dovecot <dovecot at dovecot.org> wrote: >> >> >> Hi, >> >> when trying to build dovecot 2.3.5.1 pigeonhole testsuite crashes in >> > > Which version of pigeonhole are you using? latest available - 0.5.5

Hi, I'd like to know your opinion for bug http://bugzilla.redhat.com/show_bug.cgi?id=544121 Recently serial connected UPSes stopped working because ModemManager steals tty devices (it tries to open every tty device to check if there is modem sitting there), this means device is blocked for about 10 seconds. This prevents nut daemon to start. I've reassigned bug against ModemManager

On Tue, Oct 16, 2018 at 09:25:15AM -0500, Valeri Galtsev wrote: > Hoping to not offend proponents of systemd/firewalld... Perhaps if you weren't spreading misinformation, we wouldn't be offended? > Linux kernel is already containing chunks of code related to > systemd/firewalld and friends. One can disable stuff during kernel build, > but the result it still is not like the

On Tue, Dec 29, 2015 at 5:23 PM, Joseph L. Casale <jcasale at activenetwerx.com > wrote: > Instead of converting the sysv script, you could trivially write your own, > the following > was tested against about 6 SNMP queries, the service stops and starts as > expected. > That's certainly an option. One that I was prepared to resort to. But curiosity has the best of me ...

Hi, we found a bug in ssl-params. It calls openssl DH generator for 512 and 1024 bits, but in FIPS mode, openssl won't generate anything for less than 1024, so it fails with: error:0506A06E:Diffie-Hellman routines:DH_BUILTIN_GENPARAMS:key size too small but when DH generator fails, ssl-params hangs forever in io_loop_run: __epoll_wait_nocancel() io_loop_handler_run(..) at