This is OT for mod_perl, sorry... * Cahill, Earl <[EMAIL PROTECTED]> [2002-04-29 13:55]: > > Our NIS maps are on the order > > of 3 GB per file (>64k users). > > Man, that is one big file. Guess dropping a note to this list sorta > lets you know what you have to really scale to. Sounds like dirsync > could use rsync if Rob makes a couple changes. Can't believe the file > couldn't be broken up into smaller files. 3 GB for 64k users doesn't > scale so hot for say a million users, but I have no idea about NIS > maps, so there you go.
I haven't been following the conversation, for the most part, but this part caught my eye. It is possible to split a NIS map up into many small source files, as long as when you change one of them you recreate the map in question as a whole. I've seen places with large NIS maps (although not 3GB) split the map up into smaller files, where each letter of the alphabet has it's own file in a designated subdirectory and a UID generator is used to get the next UID. When the NIS maps have to be rebuilt, the main map file is rebuilt using something like: (cat passwd.files/[a-z]*) > passwd; make passwd which, of course, could be added to the Makefile as part of the passwd target. (darren) -- OCCAM'S ERASER: The philosophical principle that even the simplest solution is bound to have something wrong with it.
