On Thu, Jul 13, 2017 at 2:01 PM, Bob Katz <bobk...@digido.com> wrote:
> >
> It's a mess and I wish I could back out of it and start from scratch.
> Also in the process I tried to create a xinet.d method of initiating
> rsync and I fear a conflict. All I did was install xinetd and create
> some config files but I can try to back out of that if you think it's
> creating a conflict.
>
If xinetd is configured to listen on the rsync port you would not be
able to start a standalone rsync daemon. Only one process can listen
for connections, so whichever started first would win. See if you
can remove the xinetd part, then use systemctl to stop and start your
daemon, then systemctl status to see if it is running, and/or
journalctl to view its logs.
--
Les Mikesesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
