title: Risks of restarting Apache?
body: <p>I just started working a company that is having me build a program for them that allows them to access a database and work with the data.  </p>
  
  <p>They currently have a solution written in PHP, but its quite outdated, and I am not familiar with PHP.  While I am building the new solution for them they asked me if I could at least just fix one issue with the current program.  It is limiting the amount of records that can be uploaded and I believe it has to do with the php.ini having an upload limitation of 2M.</p>
  
  <p>I understand that after changing this configuration setting that Apache would need to be restarted in order for the changes to take effect.  I am concerned of other issues that may arise from a reboot.  Considering that I do not know PHP very well and that this program has not been touched in over a year.  Do I risk running into issues from changing this configuration and restarting Apache?  </p>
  
  <p>I guess I just have a fear that the program will not come back up after a reboot.  Correct me if I am completely wrong for thinking this way, but I have a fear of code being loaded in RAM and if there were any changes with the code then the restart will load the new corrupted code.  I would assume it would be unlikely that the code has been touched, but you never know.</p>
  
  <p>I have been researching to try and understand the program.  So far all I can find is that it is PHP and running Apache connecting to a Mysql DB and using something called MapServer?</p>
  
  <p>Thanks ahead for your help.</p>