(old)Puppy Linux Discussion Forum

The copy command 'cp' has an option -u that might be useful in
pschedule.


With this option the copy is only made if the source file is newer.

-u, --update
copy only when the SOURCE file is newer than the destination file
or when the destination file is missing

_____________________________________________

dumb question - but I'll ask anyway.

I love Pschedule, it's doing exactly what I need it to.

As is the norm for cron, if the computer isn't powered up, and a Pschedule job is scheduled to run, the job simply won't run.

Is there any way to get Pschedule to run these deferred jobs when the computer is powered up?

I've heard that anacron can do this - can this program somehow be "tied in" to Pschdule?

Thanks for any tips (for a relative newbie)

Bill

There is a log describing when the user shutdown and reboots

/var/log/

and from that info and the crontab info it would be possible to
write a list of jobs that were missed while the computer was shutdown,
but nobody has written a script to do that ???

A francophone user complained about Lucid 528 not working with
pschedule.

http://murga-linux.com/puppy/viewtopic.php?t=85533

I suggested updating to latest gtkdialog version

don570
I have now uploaded the NLS_old package.


Thank you
Sigmund

While working on a Japanese translation of Pschedule
I came upon this odd bug...

Launch 'pschedule' from terminal

Don't put in any information for the settings.

Click the 'Add' button.

The result is gibberish line.(see image)
It doesn't cause a crash fortunately.



___________________________________________________

don570
I am glad you'd report this even if it's not critical.
Now fixed with 1.1.3


Sigmund

Version 1.1.4
See main post

Changelog
- Use icon from libstardust if available.
- Hightlight human-readable 'next run: ' in add-dialog.

Hi, thanks for this nifty little programme.

One issue:
When I schedule any task for the hour 08 or 09, pschedule tells me it's scheduled for the hour "00"

Version 1.1.5
See main post

Changelog
- Bugfix: Set hour/minute to 08 or 09 (thanks to redandwhitestripes)

version 1.1.5 - bug found

I've been testing pclock in 64 bit Quirky and I had to
remove the analog clock.

...but more importantly I tested an alarm time so that
it went off at 8:05 am every day, but it didn't work.

I investigated and other times worked, so maybe pschedule won't work
between 8:00 and 8:59 ???

I need to test more times, to be sure.
__________________________________

April 64

# pschedule
cat: /var/spool/cron/crontabs/root: No such file or directory

I think I know why pschedule doesn't work properly in Quirky 64 bit.

It's the way that the time zone is set.

Pschedule is confused by the hour. That is why it will behave properly

when I set it to alarm every 10 minutes, but it won't alarm at 5:10 am
because an hour is mentioned.

______________________________________________

I posted a comment here:

http://murga-linux.com/puppy/viewtopic. ... 710#836710

The discussion about /var/spool/cron started a long time ago (page 2 of this thread)

I haven't looked at it, and it would require some digging for me to move crontabs to /etc/crontabs since the crontab format is different (if I got it right). Atm, my IRL is a bit stuffed, so I have not the required time at this very moment.

Sigmund

I think pschedule works fine in April64. The jobs are listed properly.

pschedule knows where they stored. The following commands work
properly as well.
So I've concluded there is a bug in the crond utility.

_____________________________________________

I have fixed Pschedule, now version 1.1.5-1:

http://bkhome.org/news/?viewDetailed=00184

don570 wrote:I think pschedule works fine in April64. The jobs are listed properly.

pschedule knows where they stored. The following commands work
properly as well.

Code: Select all

crontab -e

crontab -l

So I've concluded there is a bug in the crond utility.

_____________________________________________

You need to know whether you are using the 'cron' package or the busybox applets.

I changed Pschedule to explicitly use the busybox applets, just in case the cron package is installed.

'crond' and 'crontab' busybox versions, both support the '-c' option to specify the working directory.
From the man page at die.net, the full crond does not have this option.

So in Pschedule I have "busybox crond -c /var/local/cron/crontabs"

missing minute intervall in pschedule

example: 5 Minute Intervall:

*/5****

missing minute intervall in pschedule

example: 5 Minute Intervall:

*/5****