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 selected article
Showing 1 of 919 articles.
Currently 5 other people reading this forum.


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

Login to reply

👍?
helpful
4:57pm Fri 26th Aug, ANONYMOUS

Hi! I'm thinking about how to do the project, and was hoping to get a bit of help before the weekend commences. Any guidance with the following is appreciated: 1. I am thinking that we only want to read the Estimate file once and somehow store its values, but I'm not sure how to approach this. If it was in python, I would think to just store the data in a dictionary, but I'm at loss as to how to store this - I was thinking maybe in arrays or something? 2. You mentioned that we shouldn't be going over the crontab file again and again. But I don't really understand how we keep track of all the entries otherwise - especially ones that have * and may be executed multiple times a month. Should we be going over all the crontab entries every minute to check? Secondly, is it reasonable to try and store each line of crontab in an array? 3. I am trying to think of the best way to keep track of which processes are running and then which processes are terminated. Would keeping an array of the processes running, and then removing the process once they have terminated seem reasonable? Thank you.

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