On December 25, 2017 10:25:42 PM EST, "li...@lazygranch.com" <li...@lazygranch.com> wrote: >I figured I would middle post, so skip down a bit. > >On Mon, 25 Dec 2017 11:56:02 -0800 >Gao <g...@pztop.com> wrote: > >> I quickly checked my policyd-spf setting after read your email. I >> noticed that the policyd-spf in my system is not running as a >service. >> >> I guess you are using debian. I am using CentOS7 and I installed >> pypolicyd-spf from EPEL. So is there a big advantage to running it as >> a daemon service? How do I enable it as a service? Obviously yum >> install doesn't take care of the service setup. >> >> Gao > >I'm on Centos 7. This is my uname -a. >Linux servername 3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 >UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > >Looking at ps aux, policyd-spf is not running. In the strict sense, >that means it is not a daemon. >https://en.wikipedia.org/wiki/Daemon_(computing) >However all references to policyd and policyd-spf are as daemons. > >I'm new to Centos. I run opensuse on my desktop and had presently have >my VPS server on FreeBSD. Due to update issues, I decided to abandon >FreeBSD for Centos, since I'm more familiar with Linux than BSD these >days.
Despite the name, it's not a daemon. When I started the project, I anticipated that in it's future, but later decided staying with using spawn was a good idea. I also decided renaming wasn't worth the trouble. Scott K
