MAXLOGNAME 17 ?
Hi, in my service I have one box linux runing openldap with five thousand accounts. Many servers linux do authentication in this box and everything is fine. We also use box freebsd 4, however without this feature because not works nss_ldap in this version. Well, whith the begin of the 5.1, a could see this working (thanks Vidrine). My problem is size of username, that can be bigger than seventeen caracteres. The define MAXLOGNAME in /usr/include/sys/param.h and UT_NAMESIZE in /usr/include/utmp.h show me this. I think that change this value can resolv. After one cvsup of current, my login and syslogd were compiled again but not works. Then I did one attach with gdb in login and I watched that mistake was in setlogin(username) in the child process. - May 30 18:51:57 ws-tor-0012 login: setlogin(procergs-carlos-louzada): Invalid argument - exiting - If this is true, I need recompile the kernel and libc (make world) with the new values? What can I do in this case? ps. About 5.1-beta2, my console is full of warnings: -- May 30 17:17:51 ws-tor-0012 kernel: Sleeping on stopevent with the following non-sleepa blelocks held: May 30 17:17:51 ws-tor-0012 kernel: exclusive sleep mutex sigacts r = 0 (0xc42c4aa8) lock ed @ /usr/src/sys/kern/subr_trap.c:248 May 30 17:17:51 ws-tor-0012 kernel: lock order reversal May 30 17:17:51 ws-tor-0012 kernel: 1st 0xc42c4aa8 sigacts (sigacts) @ /usr/src/sys/kern/ subr_trap.c:248 May 30 17:17:51 ws-tor-0012 kernel: 2nd 0xc4187608 process lock (process lock) @ /usr/src /sys/kern/kern_synch.c:312 May 30 17:17:51 ws-tor-0012 kernel: Stack backtrace: May 30 17:17:59 ws-tor-0012 kernel: Sleeping on stopevent with the following non-sleepa blelocks held: May 30 17:17:59 ws-tor-0012 kernel: exclusive sleep mutex sigacts r = 0 (0xc42d4aa8) lock ed @ /usr/src/sys/kern/subr_trap.c:248 -- -- milo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MAXLOGNAME 17 ?
On Mon, Jun 02, 2003 at 12:52:38AM -0300 I heard the voice of
milo, and lo! it spake thus:
I think that change this value can resolv. After one cvsup of current,
my login and syslogd were compiled again but not works. Then I did one
attach with gdb in login and I watched that mistake was in
setlogin(username) in the child process.
Yes, you can.
Just change the values, then do your buildworld/buildkernel etc. You may
also need to recompile some ports that mess with usernames. I used to do
this on 2.2.x to get 16-char usernames, and had to rebuild things like
sshd to handle it ('course, with ssh in base now, that's one less).
There were occasional weirdnesses (wtmp got screwy sometimes, never
tracked it down), but overall it worked fine.
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
