Cumulus.ini (preserving history): Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
Text replacement - "[[MXDiags" to "[[MXDiags_folder"
m (Text replacement - "[[MXDiags" to "[[MXDiags_folder")
For Cumulus MX, if it has been given a '''Cumulus.ini''' file created for Cumulus 1, then apart from a couple of parameters already mentioned, MX has all the settings it needs.
 
However, if Cumulus MX is being run for the first time and it does not inherit a file, it needs some settings before it can do anything. The difference is that MX just hangs, unless you look at the Terminal output or the file it creates in [[MXDiagsMXDiags_folder]], you won't know it is waiting for settings. You need to start up the admin interface and go into the various settings pages yourself to select what MX needs to continue to work. You then need to stop MX so it stores those settings and can use them next time it starts. Although some settings can take effect while MX is running, others only take on their new values when MX is restarted.
 
Should you accidentally delete Cumulus.ini, or should you close MX badly so it does not manage to correctly save the entire contents of Cumulus.ini, MX has an advantage in that it saves Cumulus.ini into the backup folder every time it restarts and every time it does a rollover.
{{Version badge 1}} Cumulus 1 stores this output in [[ftplog.txt]].
 
[[File:Badge vMx.png]] MX stores this output in the same [[ftplog.txt] file. However as MX allows use of alternative secure protocols instead of standard FTP, remember this file is designed for standard non-secure protocol transfers, so for secure transfers some useful information may be in standard [[MXDiagsMXDiags_folder]] file.
|-
|MaxFTPconnectRetries=3
5,838

edits

Navigation menu