During some development I have been doing frequent reboots.
I have also experienced frequent corruption of certain photon config files.
Particularly pfm and phelp config files.
When I make a consous effort to:
- exit photon
- sync
- shutdown -f
I don’t seem to get any file corruption. (This is not the result of
extensive testing, just a casual observation.) But being a mere impatient
programmer, I just don’t always do these three steps above. Also, sometimes
my system just freezes (because of what I’m developing) and so I don’t have
the opportunity of getting out gracefully.
Are there plans to correct this problem?
Also, I’ve noticed that helpviewer and pfm don’t write out their changes
until until the program terminates. I think that if those config files were
re-written as soon as they were modified it would likely alieviate this
problem.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
This would be bad for “true embedded” devices where people just expect to
hit the OFF button.
“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:9v693v$mb6$1@inn.qnx.com…
During some development I have been doing frequent reboots.
I have also experienced frequent corruption of certain photon config
files.
Particularly pfm and phelp config files.
When I make a consous effort to:
- exit photon
- sync
- shutdown -f
I don’t seem to get any file corruption. (This is not the result of
extensive testing, just a casual observation.) But being a mere impatient
programmer, I just don’t always do these three steps above. Also,
sometimes
my system just freezes (because of what I’m developing) and so I don’t
have
the opportunity of getting out gracefully.
Are there plans to correct this problem?
Also, I’ve noticed that helpviewer and pfm don’t write out their changes
until until the program terminates. I think that if those config files
were
re-written as soon as they were modified it would likely alieviate this
problem.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net