Wednesday, October 29, 2008
Environment issues - Corporate life
My Father-2
Grand Parents
My Father-1
My father is a raconteur. He used to tells me the stories of Prophet Jonah and Thobith. Thobith is a story of a father and son. But I really confused why he selects these two stories regularly. There are thousands of stories in Bible. Even now I didn’t get the reason or the driving force to tempt him to tell the same stories several times to me. But one thing I am sure I don’t exactly remember what all other stories he had told to me . When I grown I identified both stories are related to the same people from Nineveh. And also in Jonah’s story the fish swallowed the prophet. In Thobith’s story he captured the fish which came to shore to swallow him. What it really means? Is it the reason my father had selected these stories?
I love this nature!!
My Memories
What is my oldest memory? I was walking under the table and talking to my neighbour Thoman (His real name is Thomas). I was too short even to walk under table!! I planted a small areca nut tree 3 to 4 times at different places in the farm land on the same day. I was crying when my elder father and mother sold my goats to butcher. I was lying on the ‘varandha’ and watching the flowing river, flying birds, and loaded boats from Market. Sometimes I fought with Bokko( Bosco) without any reason. Bokko is my first friend in my life, I love him a lot. I was jealous of him allowed to bath in river when I was not.
I was a dark short boy, doesn’t have any charm. The boys around my home were calling me ‘UNDANPORI’. I do remember one young guy, the people around us were calling him ‘CHAKKANDI’. We fought in between regularly; at last I was not able to control my emotions and broke down. Then all around us would laugh and I went back to home. If something wrong happened I didn’t come out of home sometime. I would get inside the shell to overcome that.
I am writing my memories are not to get into a writer’s cap. Not because I have extraordinary experiences to tell to all. My intention is to write something in English as a self learning process. Thanks to INTERNET and BLOGS to give me an opportunity to publish it.
Wednesday, February 13, 2008
"Argument list too long": Beyond Arguments and Limitations
Method #4: Recompile the Linux kernel. **
This last method requires a word of caution, as it is by far the most aggressive solution to the problem. It is presented here for the sake of thoroughness, since it is a valid method of getting around the problem. However, please be advised that due to the advanced nature of the solution, only experienced Linux users should attempt this hack. In addition, make sure to thoroughly test the final result in your environment before implementing it permanently.
One of the advantages of using an open-source kernel is that you are able to examine exactly what it is configured to do and modify its parameters to suit the individual needs of your system. Method #4 involves manually increasing the number of pages that are allocated within the kernel for command-line arguments. If you look at the include/linux/binfmts.h file, you will find the following near the top:/*
* MAX_ARG_PAGES defines the number of pages allocated for arguments
* and envelope for the new program. 32 should suffice, this gives
* a maximum env+arg of 128kB w/4KB pages!
*/
#define MAX_ARG_PAGES 32
In order to increase the amount of memory dedicated to the command-line arguments, you simply need to provide the MAX_ARG_PAGES value with a higher number. Once this edit is saved, simply recompile, install and reboot into the new kernel as you would do normally.
On my own test system I managed to solve all my problems by raising this value to 64. After extensive testing, I have not experienced a single problem since the switch. This is entirely expected since even with MAX_ARG_PAGES set to 64, the longest possible command line I could produce would only occupy 256KB of system memory--not very much by today's system hardware standards.
The advantages of Method #4 are clear. You are now able to simply run the command as you would normally, and it completes successfully. The disadvantages are equally clear. If you raise the amount of memory available to the command line beyond the amount of available system memory, you can create a D.O.S. attack on your own system and cause it to crash. On multiuser systems in particular, even a small increase can have a significant impact because every user is then allocated the additional memory. Therefore always test extensively in your own environment, as this is the safest way to determine if Method #4 is a viable option for you.
Conclusion
While writing this article, I came across many explanations for the "Argument list too long" error. Since the error message starts with "bash:", many people placed the blame on the bash shell. Similarly, seeing the application name included in the error caused a few people to blame the application itself. Instead, as I hope to have conclusively demonstrated in Method #4, the kernel itself is to "blame" for the limitation. In spite of the enthusiastic endorsement given by the original binfmts.h author, many of us have since found that 128KB of dedicated memory for the command line is simply not enough. Hopefully, by using one of the methods above, we can all forget about this one and get back to work.