On Monday, Dec 22nd 2003 at 10:58 -0500, quoth Jake McHenry: =>This works without any problems so far, just ran a query with 2354 =>args.. So I'm not sure where the 1024 arg limit idea came from. I just thought I'd throw my $.02 in here on a small history lesson. Back as recently as SCO SVR3.2 days, there was a symbol in /usr/include somewhere (maybe it was called MAX_CMD or MAX_CMDBUF or something like that). It was the actual byte count of the total that the command line was allowed to be combined with the length of your total environment. This was a big deal because if you defined a dozen or so environment variables, you'd still end up with a substantial environmnet just from the contribution of running X. The number was (if I recall correctly) 5K. So really not a lot of room to play with. Back then we *all* knew how to use things like find and xargs to best advantage. Then when Solaris went with SVR4 and other SVR4 releases happened, all those kernel parameterizations that were static went dynamic. Under Solaris, I beieve you are allowed to have cmd lines that go up to a gig (not that you'd ever want to). I don't know what the limits are under Linux but I do know that we're not constricted to anything unreasonable these days. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
