run level 1, login takes too long, 2.4.X vs. 2.2.X

I had occasion to "telinit 1" today and found that it took a long time to login after root passwd was entered. this doesn't happen with 2.2.X kernels.

Is this to be expected with the 2.4 series kernels? or a bug?

Martin

strace for 2.4.0-test11-pre7

---snip---
gettimeofday({974665658, 952483}, NULL) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
getpid() = 305
bind(3, {sin_family=AF_INET, sin_port=htons(905), sin_addr=inet_addr("0.0.0.0")}}, 16) = 0
ioctl(3, FIONBIO, [1]) = 0
sendto(3, "\31\23\233@\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3"..., 56, 0, {sin_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")}}, 16) = 56

poll([{fd=3, events=POLLIN}], 1, 5000)  = 0
ioctl(3, SIOCGIFCONF, 0xbfffb33c)       = 0
ioctl(3, SIOCGIFFLAGS, 0xbfffb344)      = 0

sendto(3, "\31\23\233@\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3"..., 56, 0, {sin_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")}}, 16) = 56
---snip---

strace for 2.2.17

---snip---
gettimeofday({974664928, 735539}, NULL) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
getpid() = 368
bind(3, {sin_family=AF_INET, sin_port=htons(968), sin_addr=inet_addr("0.0.0.0")}}, 16) = 0
ioctl(3, FIONBIO, [1]) = 0
sendto(3, "_c\353\331\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3"..., 56, 0, {sin_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")}}, 16) = 56
poll([{fd=3, events=POLLIN, revents=POLLERR}], 1, 5000) = 1
recvfrom(3, 0x8056380, 400, 0, 0xbfffd66c, 0xbfffd618) = -1 ECONNREFUSED (Connection refused)
close(3) = 0
---snip---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

It looks like login is trying to contact a YP server but getting no response. Was the kernel the only configuration detail you modified?

Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

rpc.portmap isn't running, your login configuration/nss requires yp or something provided ans an RPC.

-d

begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[email protected]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Hi David,

Yup, I know rpc.portmap isn't running, the point is that it wasn't running on either 2.2.17 or 2.4.X. Isn't run level 1 supposed to only be the bare minimum of running processes, a few kernel processes, init and getty. No network services...

What's changed in the kernel to elicit this behavior?

Is there a better "faster" way to get root access at run level 1 w/o login & passwd on 2.4.X?

No it's not an everyday occurance, but I was impatiently thinking the sytem had locked up and rebooted a couple of times, so it got me wondering why 2.2.X and 2.4.X differ in this basic behavior.

Martin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/