inetd problem: IPv6 for RPC is not supported yet
Apart from disabling INET6 in the inetd build, is there any way of supressing inetd from trying to bind v6 services? I like using rup on the internal network, but it's not working on my latest-sup-current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd problem: IPv6 for RPC is not supported yet
Apart from disabling INET6 in the inetd build, is there any way of
supressing inetd from trying to bind v6 services? I like using rup
on the internal network, but it's not working on my latest-sup-current.
Sorry for your problem and please try this patch.
Now I am waiting to get commit permission.
Yoshinobu Inoue
Index: inetd.c
===
RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.77
diff -u -r1.77 inetd.c
--- inetd.c 2000/01/28 20:06:15 1.77
+++ inetd.c 2000/02/01 15:11:35
@@ -1522,8 +1522,9 @@
} else
sep-se_proto = newstr(arg);
if (strncmp(sep-se_proto, "rpc/", 4) == 0) {
- if (sep-se_family != AF_INET) {
- syslog(LOG_ERR, "IPv6 for RPC is not supported yet");
+ if (no_v4bind != 0) {
+ syslog(LOG_INFO, "IPv4 bind is ignored for %s",
+ sep-se_service);
freeconfig(sep);
goto more;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: inetd problem
On 8 Jan 1999, Dag-Erling Smorgrav wrote: Can anyone tell me if the inetd realloc (and other) problems have been fixed yet? Searching Deja News shows conflicting reports. I checked the current diffs, and built version 1.46 - is this a safe version to use? It's been running on my local workstation for a few days now, but it really doesn't have any load on it. I'd like to copy it up to our webservers, but thought I would ask first. If you mean the dying daemons problem, it has probably been fixed in version 1.105 of src/sys/vm/swap_pager.c. No. People are constantly confused over this issue. There is (was) a bug in inetd related to the way it handles signals, which caused it to output junk pointer: too low to make sense (or sometimes too high to make sense) when under heavy load. It is not the same bug as the dying daemons bug. There have been two attemps to fix the inetd bug: one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't heard any complaints about the inetd bug lately, so I'll tentatively postulate that I succeeded. Did someone bring it back? Telnet output: Escape character is '^]'. inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. Connection closed by foreign host. That's to a freshly rebooted machine (with 16 MB memory, 96 MB swap) that was doing a `make buildworld' when the X server on another machine that displayed the xterm with an rsh session to it. Since ssh ain't aware of Kerberos I'll have to attach a console to look into this further. Running 3.1-BETA, cvsup'ed Feb 10, world and kernel. Sorry, no kernel debugger :( but I'd appreciate it if someone would point me to documentation outlining how to configure the port speed in boot0/ boot1, and what option to set to still allow unattended reboots after a crash. -- Niels. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: inetd problem
: dying daemons bug. There have been two attemps to fix the inetd bug: : one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on : patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't : heard any complaints about the inetd bug lately, so I'll tentatively : postulate that I succeeded. : :Did someone bring it back? Telnet output: : :Escape character is '^]'. :inetd in realloc(): warning: junk pointer, too low to make sense. :inetd in free(): warning: junk pointer, too low to make sense. :Connection closed by foreign host. : :That's to a freshly rebooted machine (with 16 MB memory, 96 MB swap) that :was doing a `make buildworld' when the X server on another machine that :displayed the xterm with an rsh session to it. Since ssh ain't aware of :Kerberos I'll have to attach a console to look into this further. Running :3.1-BETA, cvsup'ed Feb 10, world and kernel. : :Sorry, no kernel debugger :( but I'd appreciate it if someone would point :me to documentation outlining how to configure the port speed in boot0/ : -- Niels. Please do the following: uname -a strings /usr/sbin/inetd | fgrep Id -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: inetd problem
According to Matthew Dillon: strings /usr/sbin/inetd | fgrep Id ident(1) is your friend :-) /usr/sbin/inetd: $Id: inetd.c,v 1.46 1999/01/05 11:56:35 danny Exp $ -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
