PLEASE NOTE: this server, secure.csse.uwa.edu.au, will be unavailable on Wednesday 7th December, from 1pm until 4pm (was Monday 5th).
Web-based programs, such as csmarks, cssubmit, and the help fora, will all be unavailable.
  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 3 other people reading this forum.


 UWA week 37 (2nd semester, week 7) ↓
SVG not supported

Login to reply

👍?
helpful
12:48pm Mon 12th Sep, Rados M.

Hi Chris, Is the sample solution done to the full requirements of the project (would it recieve full marks)? I ask this because the sample solution accepts a cron file input that contains a command run on the 31st of feb. Do I have to reject that as an invalid input or just accept it and not run it like the sample sol does? The project outline states that there will be an estimate for every cron entry, does the reverse hold true? Will we be given sample data when testing our code where there exists an estimate for a command that doesn't appear in the cron file? I understand that we will be given cron files that have multiple lines for the same command eg: Cron file 0 3 * * tue twice-weekly-backup 0 3 * * thu twice-weekly-backup in that case will we be given 2 different lines in the estimate file or just 1? If we are given 2 lines will those always contain the same estimate or no?


SVG not supported

Login to reply

👍?
helpful
1:02pm Mon 12th Sep, Christopher M.

Hi Rados, "Rados Markovic" <23*2*1*[email protected]*u*e*t*u*a*e*u*a*> wrote:
> Is the sample solution done to the full requirements of the project (would it recieve full marks)?
Yes (I hope so); it also implements helpful debug output, but that is not required.
> I ask this because the sample solution accepts a cron file input that contains a command run on the 31st of feb. > Do I have to reject that as an invalid input or just accept it and not run it like the sample sol does?
Do you have an example of what fails? The line: 0 3 31 1 * daily-backup is correctly detected/reported as an error.
> The project outline states that there will be an estimate for every cron entry, does the reverse hold true?
The reverse does not hold.
> Will we be given sample data when testing our code where there exists an estimate for a command that doesn't appear in the cron file?
That's a possible/reasonable thing to want. It enables us to have a huge, general, estimates file, that applies to many different crontab files.
> I understand that we will be given cron files that have multiple lines for the same command eg: > > Cron file > > 0 3 * * tue twice-weekly-backup > 0 3 * * thu twice-weekly-backup > > in that case will we be given 2 different lines in the estimate file or just 1?
Just one line in the estimates file. (if needing to support this, you could give each command a different name)


SVG not supported

Login to reply

👍?
helpful
3:14pm Mon 12th Sep, Rados M.

"Christopher McDonald" <ch*i*.*c*o*a*[email protected]*a*e*u*a*> wrote:
> Do you have an example of what fails?
I have just looked over it and realised that I inputed 2 when I meant feb by mistake Thank you.


SVG not supported

Login to reply

👍x1
helpful
3:34pm Mon 12th Sep, Christopher M.

"Rados Markovic" <23*2*1*[email protected]*u*e*t*u*a*e*u*a*> wrote:
> I have just looked over it and realised that I inputed 2 when I meant feb by mistake
Don't worry - we've all done that before :-)

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