PLEASE NOTE: the upgrades to this server, secure.csse.uwa.edu.au, have not yet been completed.
Hopefully the changes will be completed on THURSDAY 8th December.
Web-based programs, such as csmarks, cssubmit, and the help fora, will be unavailable at some time on Thursday 8th.
  It's UWAweek 49

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

Displaying the 4 articles in this topic
Showing 4 of 919 articles.
Currently 5 other people reading this forum.


 UWA week 34 (2nd semester, week 5) ↓
SVG not supported

Login to reply

👍?
helpful
12:03pm Mon 22nd Aug, Ryan W.

What does it mean to specify the day of the month and the day of the week at the same time?

In your example you show

0 10 22 7 mon deep-though

the 22nd of August falls on a Monday, so it seems that this should only run on 22nd of August, in which case, why specify the day of the week? An asterisk would mean the same thing, but in this case, it only works in cetain year.

In 2023, 22nd of August is a Tuesday. If the code were to run in this year, is it valid and simply doesn't run, or is it invalid?

Is it ok to report that the file is invalid if a command time specifies both the day of the week and the day of the month.

Also in the following example

* * 31 3 * which is 31st April (doesn't exist), should this be invalid, or simply not run, or report a warning (not an error) to say that the command will never run no matter what month or year it is?

Even though you said not to worry about leap years, I want to anyway because why not, and the answer to the above example is also relevant to leap years (29th February).


SVG not supported

Login to reply

👍?
helpful
12:04pm Mon 22nd Aug, Ryan W.

I just saw someone else ask the same question, feel free to ignore this one and answer them instead


SVG not supported

Login to reply

👍?
helpful
3:03pm Mon 22nd Aug, Alicia L.

Hello, I would like to know regarding the specification of the most number of command lines to be contained in both crontab and estimates files, should we consider 0 command lines in the files too? And for the estimates file, should there be a limit for the execution time for all the commands? For the final question, I believe that there were others asking a similar thing but I would still like to have a clarification: should we assume that the program only works for this year? since the program doesn't account the year as an input. Because I have concerns that there would be some dates that are invalid for other years e.g. 0 10 22 7 mon would be invalid for years other than 2022 since not every year has Monday as 22/7


SVG not supported

Login to reply

👍x2
helpful
3:09pm Mon 22nd Aug, Christopher M.

Hi Alicia, After this morning's labs we made a few changes to the wording, so you may like to re-read parts of the page again. "Alicia Lau" <22*5*0*[email protected]*u*e*t*u*a*e*u*a*> wrote:
> I would like to know regarding the specification of the most number of command lines to be contained in both crontab and estimates files, should we consider 0 command lines in the files too?
Files with zero lines should be permitted - they just indicate nothing to be done.
> And for the estimates file, should there be a limit for the execution time for all the commands?
No process will execute beyond the month in which it starts, so a limit of 31*24*60 minutes.
> For the final question, I believe that there were others asking a similar thing but I would still like to have a clarification: should we assume that the program only works for this year? since the program doesn't account the year as an input. Because I have concerns that there would be some dates that are invalid for other years
Requesting a particular month implies it's only for the current year (which will only be tested for 2022). Hope these answers help,

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy