Thankyou NIck.
You have done most of the heavy lifting for me.
Did what you suggested and working fine (did a few reboots to test). Thanks.

Thank god, i did not have to do it via loading a program into memory, and polling connection every X minutes. this is a much better way to achieve the result I am after.
Thank you for your time.
zack

Nick Thankyou.

You're instincts are correct, I do wish to have a date/timestamp. among other things.
but this is a great start.(tested and works) even this would be semi satisfactory. Is there anyway to add a date/time to this?

thanks for your help.

After your first couple of posts you are allowed to post without approval so you should be OK now.

No you don't have to do what you are proposing, but you can if you insist. If you run your program from the /etc/ppp/ip-up/local file just by adding a line to the file. /etc/ppp/ip-up and /etc/ppp/ip-up.local should only fire each time PPPoE gets a new IP. No need to have something sitting in memory looping.

Have a look at bash scripting. If all you want to do is add an IP address to a file, you can do it in a single line:

echo `ifconfig enp2s0 | awk '/inet / { gsub(".*:", "", $2) ; print $2 }'` >> my_file.txt

You could add the line to the end of the /etc/ppp/ip-up/local file or to a separate file and call the file from /etc/ppp/ip-up/local.

I have a feeling you may want more than that, perhaps at a minimum with a date/timestamp. Also that is only building a text file of IP's rather than some sort of conventional database.

Yeah Sorry Nick,I'm new so I think I not permitted to post without approval.
I realized about 30 seconds after I posted that I would like to have it run every time the IP changes. As sometimes my connection drops from my rsp/isp and I wish to log this new ip.

Sorry for the confusion,

So it would be better to have a program loaded in memory and testing every X minutes for a connection.

Initially, all I wished to achieve is ro run a program on boot. all this program would do is get the IP address and add this to a DB.

I guess what I want is, to have a program load on boot, sit in memory and test the IP address every Xminutes /or whenever it changes then, if the ip address has changed log this NEW ip in DB

something like machine boots/reboots
After IP is assigned via PPPoE
the program runs, then logs that IP to DB

program checks every x minutes for a IP, if it has changed since last IP log to DB else do nothing

Just not sure how to get a python program to run on boot? (or even if python is the best solution?)
or how to test for ip change every x minutes? or if there is a better way to do this?


Hope that is a bit clearer .

Thanks
zack

ClearOS will always test if you're connected to the internet and, if not, try to establish a connection. That is the purpose of the syswatch daemon.

If you want something to always run on boot, you can call it from /etc/rc.d/local but you have to make /etc/rc.d/local executable ("chmod u+x /etc/rc.d/local"). The only danger is you can't control when it runs. Looking at my boot log and messages log it looks like mine is running almost immediately after the network comes up.

What is it exactly that you are trying to do?

Also do you want to do it only on boot or every time your IP changes?

Thanks Nick.
I'll be trying that!
I am using PPPoE.
You may be right that having it run last is not really important.
I was hoping not to have to have it ALWAYS loaded in memory testing if it's connected to INET. But I can see how that would work.
Was hoping it just have A PROGRAM run on boot? (like windows startup) I'm far from a linux person. Is this possible?
somehow insert the program into the startup boot process. excuse my lack of working linux knowledge.
again thank you for a couple of ideas.
zack.

You can pick out your IP address with something like:

ifconfig enp2s0 | awk '/inet / { gsub(".*:", "", $2) ; print $2 }'

replacing enp2s0 with your interface. I have no idea how to get it to run as the last thing during startup as startup is asynchronous. You'll have to search the systemd/systemctl manuals and perhaps use something like a network-online target.
For a different approace, depending if you use PPPoE or DHCP there are different exit hooks you can latch onto. For PPPoE have a look at /etc/ppp/ip-up and for DHCP have a look at dhclient-exit-hooks, perhaps with the reasons "BOUND" and "REBOOT". They should trigger every time you IP changes or gets renewed.