ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I developed a control program for an Imagenex 881A sonar head. As the whole system shall be deployed in the sea and run autonomously I would like to add the following functionality:
After the n-th boot-up of linux (e.g. after 5 boot-ups) not the standard contoll programm shall be started but a slightly modified version. The problem is that this shall only happen after the n-th boot-up.
How can I solve this problem? Cron does not seem to be very helpfull in my eyes. I was thinking of a shell script that saves the amount of boot-ups in a file and reads it after the n-th boot-up. Then after 5 boot-ups the modified version of my control program will be started.
Now you just have to modify your script to accept the start and stop arguments, just like every other service script in init.d. On start (link in rcS.d on Debian) you check the value, maybe run the program, and possibly set the value back to 0. On stop (rc0.d) you increment the value - but you have to do this at a time when the filesystem is still mounted r/w. At the moment your script is written so that everything happens at once (always incremented and checked), which is the wrong way to do it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.