72 replies to this topic

[Pr2]

Normally in cron there is not path search, so I guess that you should put the full path to access awk too in your crontab command.

[WanWizard]

Yes, absolutely.

[Qu@rk]

Thank you very much guys for your replies.

So the time must have already been set before the message log starts.

Why would there be the correct time after a deep standby?

 

I can only describe what's happening and post logfiles.

If you do not have time to read my posts completely I understand but there is nothing I can do about it. I am sorry.

 

I did a lot of research and testing before doing this.

 

As I mentioned several times, the command line in crontab works perfectly fine if the box is already running and the crontab entry was set to a time in the near future for example or to be executed every 15 minutes. It just doesn't work when the box awakes from deep standby by a timer event.

 

Is there a way to preserve the messages logfile between reboots or do I have to write my own script (init.d) for that to have a way to check what was happening at night?

[WanWizard]

If can only happen if the network was started, and the corresponding ntpdate fired, before syslog started. Unlikely, but possible.

 

You can preserve your logs by not storing them in volatile storage. The path is configured in /etc//syslog-startup.conf.

[Qu@rk]

Thanks.

Well, I checked several times and my syslog "messages" always shows the correct time from line 1, even after several hours in deep standby.

[WanWizard]

You may have a very fast box with ditto ethernet negotiation speed.

 

But I'm still waiting for the answers to all other questions, as there is plenty wrong with your command ( like a missing path for awk ).

 

I'd start by scheduling something like

10 3 * * * echo "TEST" | ts '%Y-%m-%d %H:%M:%S >> /media/hdd/test.log

simple, without any dependencies, or other things that could go wrong with the command. And when that works, built it up.
 

Also note that unless you've installed the "full-fat" packages, you're working with busybox, which has only a small subset of options available on a desktop OS.

[Qu@rk]

Thanks for your reply.

As mentioned several times and last in Post #63, the command line in my crontab works perfectly fine.

As I mentioned several times, the command line in crontab works perfectly fine if the box is already running and the crontab entry was set to a time in the near future for example or to be executed every 15 minutes. It just doesn't work when the box awakes from deep standby by a timer event.

Yes, I am working with busybox (standard OpenPLi 8.3) and I am aware that there are many limitations.

 

I did not know about the package "full-fat", interesting. But I don't want to change too much on my box. The more I deviate from standard OpenPLi the more complex testing and investigating becomes.

 

Btw, awk and tee work in crontab with or without the path to their location (/usr/bin).

 

I did not know the ts command. Makes things a bit easier. I use awk from time to time, very powerful, but for simple things it's a bit clumsy.

 

I have used tee because I was not sure if stdout is still needed for a cron log or something like that.

 

Thank you very much again for your useful hints.

Edited by Qu@rk, 21 August 2024 - 08:36.

[Qu@rk]

Also note that unless you've installed the "full-fat" packages, you're working with busybox, which has only a small subset of options available on a desktop OS.

 

I couldn't find anything about the "full-fat" packages. Please, could you point me in the right direction, link, docu etc. Thanks.
 

[s3n0]

Normally in cron there is not path search, so I guess that you should put the full path to access awk too in your crontab command.

Or let him create a shell script that runs in a regular Shell interpreter - as I suggested before. And there everything will work as it should work properly in Linux. The disadvantage is the need to create one more file (shell script) on the disk in the set-top box.

 

@Qu@rk:

 

Why do you actually need deep standby ? Why don't you use classic standby ? For what reason ? Is it some very important problem or why ?

[Qu@rk]

I was surprised too that tee and awk work in busybox crontab without a path.

I have tested both versions. But I have included the path in my recent version. It doesn't make a difference but you never know.

 

@s3n0

In Germany electric power is very expensive.

If you live in a country with very low energy prices or maybe money is no issue of course "normal" standby is more convenient.

I have used deep standby for more than a decade on my boxes and all these boxes have always worked perfectly fine without any issues.

 

Thank you all very much for your support and your time, very kind.

 

What are these "full-fat" packages? Couldn't find anything about it. Only the bash packages.

Edited by Qu@rk, 21 August 2024 - 15:10.

[WanWizard]

Not all tools have a "full-fat" equivalent in the feed (either because it doesn't exist, or we don't build it).

 

For awk for example, GNU awk is available in the feed, which has a lot more features that the crippled busybox version.

root@vuduo4k:~# opkg list | grep awk
gawk - 5.1.0-r0.1 - GNU awk text processing utility

Same for example for "bash" vs the cripped busybox ash shell:

root@vuduo4k:~# opkg list | grep bash
bash - 5.1-r0.1 - An sh-compatible command language interpreter

 

[Qu@rk]

Oh je, hihi, I was completely on the wrong track.

 

Thank you very much, that makes it much clearer.

From what I was able to research there is also a full featured cron package (cronie?).

[WanWizard]

From what I was able to research there is also a full featured cron package (cronie?).

 

Yes, it is default as of OpenPLi 9.0.