Re: [6.3] How are those daemons started?
On Mon, 31 Mar 2008 23:00:39 +0200 Mel [EMAIL PROTECTED] wrote: On Monday 31 March 2008 22:27:55 Gilles wrote: On Mon, 31 Mar 2008 15:06:20 -0500, Erik Osterholm [EMAIL PROTECTED] wrote: Also note /etc/defaults/rc.conf which is /why/ these services are on by default. Entries in /etc/rc.conf override entries in /etc/defaults/rc.conf, so you should never change /etc/defaults/rc.conf. Thanks guys. After reading /etc/defaults/rc.conf, I understood that the reason there's sendmail listening on TCP25 is so that local daemons can send e-mail to the admin. Somewhat. Most daemons can do fine without the socket listener and invoke /usr/sbin/sendmail by default. Only ones that can't get to /usr/sbin/sendmail (i.e.: chrooted daemons), but in my experience they don't know how to talk SMTP either. As I understand it, modern versions of /usr/sbin/sendmail are just a frontend to the socket, so that they don't need to run setuid. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[6.3] How are those daemons started?
Hello By running netstat -an, I notice that some daemons are running, even though nothing is listed in either /etc/rc.conf or some equivalent in /usr/local/etc/ : tcp4 0 0 127.0.0.1.25 udp4 0 0 *.2727 *.* udp4 0 0 *.2727 *.* udp4 0 0 *.514 *.* nmap seems to only handle TCP (TCP2000 = callbook?) doesn't say which application is opening those ports, and lsof | grep doesn't return anything :-/ Are there other ways to start daemons besides listing them in /etc/rc.conf? Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Monday 31 March 2008 21:47:42 Gilles wrote: Hello By running netstat -an, I notice that some daemons are running, even though nothing is listed in either /etc/rc.conf or some equivalent in /usr/local/etc/ : tcp4 0 0 127.0.0.1.25 udp4 0 0 *.2727 *.* udp4 0 0 *.2727 *.* udp4 0 0 *.514 *.* nmap seems to only handle TCP (TCP2000 = callbook?) doesn't say which application is opening those ports, and lsof | grep doesn't return anything :-/ port 25 is sendmail, enabled by default /etc/defaults/rc.conf. 514 is syslog, also on by default. 2727 udp, no idea, but sockstat(1) will tell you. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Mon, Mar 31, 2008 at 09:58:50PM +0200, Mel wrote: On Monday 31 March 2008 21:47:42 Gilles wrote: Hello By running netstat -an, I notice that some daemons are running, even though nothing is listed in either /etc/rc.conf or some equivalent in /usr/local/etc/ : tcp4 0 0 127.0.0.1.25 udp4 0 0 *.2727 *.* udp4 0 0 *.2727 *.* udp4 0 0 *.514 *.* nmap seems to only handle TCP (TCP2000 = callbook?) doesn't say which application is opening those ports, and lsof | grep doesn't return anything :-/ port 25 is sendmail, enabled by default /etc/defaults/rc.conf. 514 is syslog, also on by default. 2727 udp, no idea, but sockstat(1) will tell you. -- Mel Also note /etc/defaults/rc.conf which is /why/ these services are on by default. Entries in /etc/rc.conf override entries in /etc/defaults/rc.conf, so you should never change /etc/defaults/rc.conf. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Mon, 31 Mar 2008 15:06:20 -0500, Erik Osterholm [EMAIL PROTECTED] wrote: Also note /etc/defaults/rc.conf which is /why/ these services are on by default. Entries in /etc/rc.conf override entries in /etc/defaults/rc.conf, so you should never change /etc/defaults/rc.conf. Thanks guys. After reading /etc/defaults/rc.conf, I understood that the reason there's sendmail listening on TCP25 is so that local daemons can send e-mail to the admin. Thanks for the tip, and sockstat: # sockstat | grep 2000 root asterisk 593 17 tcp4 *:2000*:* # sockstat | grep 2727 root asterisk 593 10 udp4 *:2727*:* # sockstat | grep 514 root syslogd531 7 udp4 *:514 *:* # sockstat | grep 25 root sendmail 676 3 tcp4 127.0.0.1:25 *:* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Monday 31 March 2008 22:27:55 Gilles wrote: On Mon, 31 Mar 2008 15:06:20 -0500, Erik Osterholm [EMAIL PROTECTED] wrote: Also note /etc/defaults/rc.conf which is /why/ these services are on by default. Entries in /etc/rc.conf override entries in /etc/defaults/rc.conf, so you should never change /etc/defaults/rc.conf. Thanks guys. After reading /etc/defaults/rc.conf, I understood that the reason there's sendmail listening on TCP25 is so that local daemons can send e-mail to the admin. Somewhat. Most daemons can do fine without the socket listener and invoke /usr/sbin/sendmail by default. Only ones that can't get to /usr/sbin/sendmail (i.e.: chrooted daemons), but in my experience they don't know how to talk SMTP either. I guess it's legacy that MTA's start their SMTP listener by default. You can set sendmail_enable=NO in /etc/rc.conf to disable the listener. If you set it to NONE sendmail will be totally off and all mail from daemons invoking /usr/sbin/sendmail will end up in /var/spool/mqueue without being processed further. If you choose to go with the NO option, be sure to read and update /etc/aliases. The difference between mail stacking up in /var/spool/mqueue or /var/mail is only the packaging. Informative reading: newaliases(8), crontab(5) and periodic(8). -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Mon, 31 Mar 2008 21:47:42 +0200 Gilles [EMAIL PROTECTED] wrote: Hello By running netstat -an, I notice that some daemons are running, even though nothing is listed in either /etc/rc.conf or some equivalent in /usr/local/etc/ : tcp4 0 0 127.0.0.1.25 udp4 0 0 *.2727 *.* udp4 0 0 *.2727 *.* udp4 0 0 *.514 *.* nmap seems to only handle TCP (TCP2000 = callbook?) doesn't say which application is opening those ports, and lsof | grep doesn't return anything :-/ Are there other ways to start daemons besides listing them in /etc/rc.conf? Thank you. You can stop syslog from listening by adding this to rc.conf: syslogd_flags=-ss -- Regards, Ghirai. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] How are those daemons started?
On Tue, 1 Apr 2008 01:47:11 +0300, Ghirai [EMAIL PROTECTED] wrote: You can stop syslog from listening by adding this to rc.conf: Thanks. I'll probably turn off Sendmail and Syslogd, and see if it works, although this host is already behind a firewall and those ports are not mapped through. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
