I am trying to learn a little about ALOHA table service, I have seen these files at various times and wonder what they do, and where they come from. I have seen support people delete some of them, but I don't understand why?
okay, cool and thank you!
Would I normally find the Lock files on the BOH? Or do they reside on the terminal they are logged into?
It sounds like the stop file is sent from the BOH to FOH? I think I remember a terminal continually rebooting and they deleted a stop file from the terminal? (not positive, was long ago)
These files are deleted from the BOH data folder. The issue with terminals that keep rebooting is a file called exiting and it will be in the tmp folder. Its purpose is to keep employees from exiting Aloha to the desktop. If someone where to ctl-alt-delete and try and stop aloha from running this marker cause the computer to reboot and sart Aloha. Sometimes it hangs and has to be manually deleted.
Okay, so a user logs onto a terminal, and a lock file is placed in the BOH data folder, to prevent them from logging in multiple terminals, and when they log off that terminal, that lock file is removed...
I didn't know about the exiting file, but I do know that if we shut down Aloha, we have to stop iber also...
If we do a refresh from BOH, does BOH send a stop file to the terminals causing a reboot?
The STOP file is created in the Aloha\TMP folder on the BOH only. It is used as a marker file to STOP the FOH for refreshes and for severe errors such as out of hard disk space.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.