I want to address the nasty problems about reading a flat text in ASCII, UTF* explicitly excluding HTML, EBCDIC, and other encoding. According to Wikipedia there are at least 8 variations of control characters.
CR+LF is typical for Windows
LF is typical for the Linux/UNIX world
CR is Mac's favorite
As you can deduct from the names the inspiration comes from mechanical typewriters.
Have just deployed IRIS in Azure and when accessing the filesystem through SSH I just can't see the ISC folder through the WSL ubuntu user, what am I missing here?
As I want to create new folders and use the same in test productions. the needed directories are created in /home/azureuser but the same is not visible in IRIS file system
While creating my latest examples for the JavaContest I faced the need to communicate with my code from a program in IRIS to my Java code.
Communication with |CPIPE| worked as READ or WRITE but not both? In the Documentation Named PIPEs are explained rather shortly. "Once open, a pipe acts like an ordinary device." Not so precise. I failed to achieve my expected READ/WRITE as TCP would offer.
I'm currently conducting tests using the docker image intersystemsdc/irishealth-ml-community:latest. I'm accessing the Linux terminal and attempting to utilize the superuser functions, but I'm encountering an issue with the password. Could someone assist me, please?
I am looking to run IRIS for UNIX on the Linux Ubuntu 22.04 platform and need to determine which filesystem configurations are considered supported. The three options under consideration are Ext4, LVM with Ext4, and OpenZFS. Currently, the system is running on a raw Ext4 filesystem, but there is a desire to switch to either LVM with Ext4 or OpenZFS to make it easier to handle disk usage.
This leads to two questions:
Are either of these two configurations considered to be tested and supported by InterSystems?
I'm having a few issues with keeping Ubuntu happy and stable, and it seems to be something at the OS level rather than within IRIS itself. My thought is to simply pare back the stuff that Ubuntu LTS runs by default, which will free up system resources (which really shouldn't be a problem, but it might help) and reduce the amount that can go wrong.
Are there any guides as to what can be safely disabled at boot time, or are required to be enabled?