Lines Matching full:it
3 version of cron. it is presented here for its entertainment value.
21 This allows "1,3,5-7", which the current cron doesn't (it won't
37 (Actually, I believe, it is because /etc/rc, which runs cron, doesn't
41 provide some reasonable defaults (if it isn't supplied by cron's
75 << Good idea, but bob@acornrc beat you to it. I used '/' instead of
97 I'm not sure if it is in cron (either SysV or BSD ... if it is, I haven't
98 figured it out ) but a comment feature would SURE BE NICE!.
100 for a period of time; it might also make it a lot more legible.
103 that one BSD4.2 cron I've used had it. I don't know about SysV. >>
114 This would seem to work best if done by cron, as it is now I have a google
116 it.
131 1. Run it through the C preprocessor via "/lib/<whatever>".
134 to do it that way, you could do it yourself (since users can
146 implement it. Cron currently doesn't keep track of the last time
150 execution around, and purge it when the crontab was overwritten.
151 This is too much work for me, but if someone adds it, let me know. >>
167 month, AND on Monday thru Saturday; which probably means running it
192 in a crontab entry. I'd assumed that it was
194 But it's really
207 Log files! It would be nice to be able to specify a log for cron
209 The latter can of course be done with > and 2> but it would be nice if
220 command might be ambiguous (with other commands). In short, it's
242 BTW, "compiled in" means that it's in a .h file, easily changed
244 don't have to go digging through the code to find it... >>
256 1) Sunday is both day 0 and day 7, so it complies with both SysV and
259 << Good idea. I did it too, thanks for informing me. >>
265 use it.
267 << I don't use 'at', and my cron doesn't do anything with it. To run
282 characters, which makes it hard to run on SysV. At least one person
283 was working on a port, but I don't know how it's going. That might
287 won't want my cron, since it doesn't add much to the standard
289 portable to non-BSD systems, since it relies on interval timers (I
291 allow). The port would be trivial, and I will do it if a lot of
292 people ask for it... >>
313 will inherit the environment of the user). If nothing else it is critically
322 are work arounds, but only putting it in cron will really work. This is
329 you define it in the shell before starting my cron daemon. However,
336 problem with cron and TZ when I used it. >>
341 Obviously this should be optional, but it would be nice if there were a
342 way to flag an entry so that it wasn't logged at all unless there was an
366 many people request it, I won't be needing -q as you've defined it.
377 it in a crontab? Suggestions, enlightenment, etc ?? >>
386 children in the cron program itself? Our cron does this and it's the pits
401 detect holidays under Unix(TM); if there were, I'd use it. As
402 it is, I'll leave this for someone else to add.
404 I can see the usefulness; it just doesn't quite seem worth it. >>
414 daemon wakes up, it sees it, and re-reads the crontab files.
416 I thought of handling the signal; even implemented it. Then this
417 clever idea hit me and I ripped it all out and added a single
421 execute it again after a certain period. This is useful if you have some
426 I'll think about it. >>
433 It would be nice if nonprivileged users can setup personal crontab files
446 The System V cron is nice, but it has a few annoying features. One is that
448 cron commands." I wish it would say WHICH cron command.
453 Another problem is with timezones. It is necessary to specify TZ=PST8PDT (or
454 whatever) when you invoke cron (from inittab, or /etc/rc) and it is also
455 necessary to add TZ=PST8PDT to each crontab line which might need it. Cron
457 it should be possible to put a line in the crontab file which overrides that
469 I seem to remember that cron keeps it open, too; so you can't even have
470 something go and periodically clean it out.