Re: Large UIDs (>65536)
Good point :) I just got a little freaked by these friendly warning messages from pwd_mkdb: "/etc/pw.Z26392" 15 lines, 319 characters chpass: updating the database... pwd_mkdb: 14 > recommended max uid value (65535) chpass: done I know the many UNIXes still have a cap at 65535 (is Linux one of them?), and I interpeted that as an error message, not a warning. I was silly :) Yann On Fri, 09 Jun 2000, you wrote: > > Hi, > > > > I was just wondering if anyone has considered allowing larger UIDs > > (unsigned long) on a FreeBSD system? What would this require changing? > > From what I can tell, the code is typedefed so if you go recompile > > everything, you should be ok. Am I missing anything here? > > How about this line from : > > typedefu_int32_t uid_t; /* user id */ > > It pays to do your own research - then you only get to look silly in > front of yourself. 8) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Large UIDs (>65536)
Hi, I was just wondering if anyone has considered allowing larger UIDs (unsigned long) on a FreeBSD system? What would this require changing? From what I can tell, the code is typedefed so if you go recompile everything, you should be ok. Am I missing anything here? Yann To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cisco Port Grouping w/FreeBSD
Hi, I have a question for the networking gurus out there. How exactly would you configure a FreeBSD machine connected to a Cisco switch with port grouping on two Ethernet channels? Also, for future reference, the funny network delays on the switched network were solved. It turns out if you force the switch to 100/full on the port, the Intel PRO 100/B card will run at 100/half, since it assumes the switch is a non-autonegotiating hub. Use auto select on both sides works very well. Yann -- Yann Ramin [EMAIL PROTECTED] Atrus Trivalie Productions www.atrustrivalie.eu.org irm.it.montereyhigh.com Monterey High ITwww.montereyhigh.com ICQ 46805627 AIM oddatrus Marina, CA "All cats die. Socrates is dead. Therefore Socrates is a cat." - The Logician # fortune "To be responsive at this time, though I will simply say, and therefore this is a repeat of what I said previously, that which I am unable to offer in response is based on information available to make no such statement." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Funny Network Transit Delays
-BEGIN PGP SIGNED MESSAGE- Hi there. I have an interesting problem (figured it out myself) but I'm wondering why it is occuring. I have a setup with Two FreeBSD machines (3.2 and 4.0 RELEASE), a Windows machine, and a NetBSD machine. The NetBSD machine has three 3Com 3C509/B NICs (ISA) and acts as a router to three subnets, one per machine. When I FTP something from the 4.0 to the 3.2 box, performance sucks. And not that the NetBSD machine is too slow, it seems neither the 4.0 or 3.2 is using the network like it should. Looking at the hub, I'm getting a pattern like this: Activity(3 secs) -- Pause (4 secs) -- Activity (2 secs) -- Pause (1 sec) -- Activity (7 secs) -- Pause (7 secs) and on for a total throughput of 80KB/s. The same occurs from Windows to the 4.0 box with Samba. I tried installing FreeBSD on the router, with no luck. The only solution I could come up with was to: sysctl -w net.inet.tcp.sendspace=2900 sysctl -w net.inet.tcp.recvspace=2900 This brings performance up to about 400KB/s, which is "ok" because of the extra latency of the router. I have another similar situation with two 4.0 boxes and iMacs running on two Cisco Catalyst 2924XL switches. If I use a plain vanilla 10Base hub I get a cool 620KB/s. Does anyone have any idea what is causing this? Yann -- ---- Yann Ramin [EMAIL PROTECTED] Atrus Trivalie Productions www.atrustrivalie.eu.org irm.it.montereyhigh.com Monterey High ITwww.montereyhigh.com ICQ 46805627 AIM oddatrus Marina, CA "All cats die. Socrates is dead. Therefore Socrates is a cat." - The Logician # fortune "To be responsive at this time, though I will simply say, and therefore this is a repeat of what I said previously, that which I am unable to offer in response is based on information available to make no such statement." -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use MessageID: FUGyzVH4vQLKyp0A67Qx1eOXvDr2V38A iQA/AwUBORzT6jEK6loGD1TnEQK9/QCg5+2Jaxj+BzYd0JkHCPoYMRgLsVoAnjp3 8t3n4rO9Oyr+R086nXwG5Asb =/RT8 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: LDAP NIS replacement
Perfect ! Please let me know when you get NSS working in the C library, as I am very interested. I tried compiling the copy of nss_ldap from padl.com - in both GNU_NSS mode and IRS_NSS mode. Both crapped out in various places and it seemed such a big chore to try to clean them up, so I stopped. I'm going to get ADP (some 486 in the corner) to 4.0-CURRENT sources, and use that as a reference platform for pam. I'm rebuilding pam_ldap from scratch, as the sources from padl once again passed through too many hands - I think it needs a fresh start. About the e-mail, sorry about that. I was typing away in my ISPs dated webmail system. NPS (Naval Postgrad School, I work there over school breaks) recently installed a new firewall, which blocks port 25, so I'm pretty stuck (their mailserver doesn't do realying :(). Yann On Tue, 14 Mar 2000, you wrote: > On Tue, Mar 14, 2000 at 04:23:32PM -0800, yramin wrote: > > Hi, > > > > New to the list, but I'm looking into developing a way to > > authenticate and grab user information from an LDAP server compared > > to /etc/passwd and company, or NIS. I was poking around the library > > code and noticed that FreeBSD does not have NSS (name service > > switch) support (otherwise I would use nss_ldap already out there - > > it doesn't compile under FreeBSD even with IRS use enabled, I've > > tried ). What would be the best way to write new getpwent(), > > etc. routines for FreeBSD? I could stick them into a library and > > have programs that want to use them link to it, but that is a pain > > (although quite portable :)). > > I'm working on a PAM system first (yes, pam_ldap is out there, but > > it sucks, lots of linuxisms), but would be interested getting some > > work done on this as well. Any thoughts, advice, pointers? > > PLEASE use the enter key about every 80 characters... your email > looks horrible ;) > > I'm working precisely on this. I've integrated the NSS functionality > from NetBSD into the standard C library of FreeBSD. I'm in the > process of rewriting the get* function to use the dispatcher. > > Once we have that, the way to go would be to have the C library > dlopen the required modules as PAM does. > > Are you sure that nss_ldap doesn't compile on freebsd? I think I > compiled it once (and of course it was unusable since FreeBSD > lacks NSS). > > regards, > > -oscar > > -- > pgp public key: finger [EMAIL PROTECTED] > pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Yann Ramin [EMAIL PROTECTED] Atrus Trivalie Productions www.atrustrivalie.eu.org irm.it.montereyhigh.com Monterey High ITwww.montereyhigh.com ICQ 46805627 AIM oddatrus Marina, CA "All cats die. Socrates is dead. Therefore Socrates is a cat." - The Logician # fortune "To be responsive at this time, though I will simply say, and therefore this is a repeat of what I said previously, that which I am unable to offer in response is based on information available to make no such statement." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
