Change Details

Do not collect remote logging sources in a peerlist. Instead add those `struct peer` sources right into the socklist. This is done after initialization anyway and the peerlist is not accessed again. The addsock() and socksetup() functions are rearranged to accomidate this change. Remote sources are now setup as sockets from the start.

Add logging sockets directly to the socklist, unless parsing flags. The peerlist is still needed to temporarily hold socket information until the configuration flags have been parsed. It is tempting to remove the entire peerlist, but addsock() does can not determine if syslogd is in secure mode unless the flags have been parsed. Also, call pidfile_open() right after flag parsing so we can terminate if another syslogd instance is already running.

Do not collect remote logging sources in a peerlistAdd logging sockets directly to the socklist, unless parsing flags. Instead add thoseThe `struct peer` sources right into thepeerlist is still needed to temporarily hold socklist. This is done afteret information until initializthe configuration anyway and the peerlist is not accessed againflags have been parsed. The addsock() and socksetup() functions are rearranged to accomidateIt is tempting to remove the entire peerlist, but addsock() does can not this change.determine if syslogd is in secure mode unless the flags have been parsed. Also, Remote sources are now setup as sockets from the startcall pidfile_open() right after flag parsing so we can terminate if another syslogd instance is already running.