Finally solved FACTS crashing issue
I've been trying to solve a customer's bbx2 problem for two years. We've had all kinds of "experts", all kinds of advice, and all along I have felt it had to be the application or bbx rather than the OS or any equipment problems.
What was happening was that the application (FACTS) would randomly "blow up" - it would turn on transparent print on the terminals (actually terminal emulators) and lock up solid, sending anything on the screen to the users printer if they had one and just locking up otherwise. This was variously blamed on the file system, the terminal emulator, OS tuning and more, but nothing fixed it.
It shouldn't have taken this long to discover the root of the problem, because it simply was lack of terminal definitions in the config.bbx file. That file has "alias" entries that look like this:
alias TF /dev/ttyi1b term alias TG /dev/ttyi1c term alias TH /dev/ttyi1d term alias TI /dev/ttyi1e term alias TJ /dev/ttyi1j term alias TK /dev/ttyi1g term alias TL /dev/ttyp4 term alias TM /dev/ttyp6 term alias TN /dev/ttyp2 term alias TO /dev/ttyp3 term alias TP /dev/ttyp0 term alias TQ /dev/ttyi1m term alias TR /dev/ttyi1n term
Interestingly, you see "ttyi" entries in there, but two years ago we switched them to a complete network setup, so now all users are on pseudo tty's - ttyp1, ttyp2 etc. Unfortunately, at the same time we had also upgraded hardware and the OS, so this important detail got forgotten. The problem came when they had enough people logged in that the ttyp assigned wasn't defined by an alias. The clues to that were there all along, and it is amazing I kept missing it, but the fix at least was simple: change the unneeded ttyi entries to define more ttyp devices. The crashing was random because it depended on how many people tried to login - a number that was usually low enough to be satisfied by the existing configuration.
I had felt some time back that pseudo tty's were involved, so I had increased the number and made sure they were defined in /etc/ttytype, but had never looked at the config.bbx file (I don't know much about bbx and was relying on other people for that).
All fixed now. Great relief all around.
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic
Inexpensive and informative Apple related e-books:
Take Control of OS X Server
Take Control of Preview
Take Control of the Mac Command Line with Terminal, Second Edition
Yosemite Crash Course
Photos for Mac: A Take Control Crash Course