Frequently Asked Questions

PCI compliance refers to the law around financial transactions, specifically credit/debit card transactions. A certain level of security is required in order to be allowed to facilitate these transactions. If you accept payments via credit card and want to run them through your sever, then the connection between your server and the payment network must have a minimum required level of security.
 
This security is encoded in the transfer protocol between your server and the payment network, which is called “Transport Layer Security”, also known as “TLS”. Because of recent changes in the law, you must have the most up-to-date version of TLS (at least version 1.2). You will fail a PCI compliance certification if you do not have the right version of TLS.
 
Additionally, this TLS update can affect some other programs on your server. Specifically, this can affect your ability to log in to your server remotely via a program called SSH (“Secure Socket Shell”). The most up-to-date version of SSH available on legacy versions of SCO (i.e., 5.05, 5.06, 5.07, 5.07V, and 6.0) does not play well with the necessary TLS version. Contact us to get a custom version of SSH that works with legacy versions of SCO that also meets PCI compliance standards.

Slow network connections can be caused by a network that is having an Internet or DNS connection issue.  If your system is Internet aware look the following file /etc/resolv.conf and see if you have a line in it called hostresorder.  Below is an example:

hostresorder local bind

nameserver 4.2.2.2

nameserver 8.8.8.8

The top line tells the system to look at /etc/hosts file and then the Internet to examine an incoming connection.    The next two lines are DNS servers used by the server to find systems on the Internet.  Add all your local IP's to the /etc/hosts file so the system can find them quickly

First try pinging a public site like yahoo.com.    You should see results like below.

# ping yahoo.com
PING yahoo.com (98.139.183.24): 56 data bytes
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=0 ttl=48 time=42.049 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=48 time=35.082 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=48 time=34.286 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=48 time=34.725 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=4 ttl=48 time=39.327 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=5 ttl=48 time=35.846 ms

If you get no results try pinging by IP nunber,

# ping 98.139.183.24
PING 98.139.183.24 (98.139.183.24): 56 data bytes
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=0 ttl=48 time=41.216 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=48 time=39.591 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=48 time=35.973 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=48 time=42.332 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=4 ttl=48 time=41.275 ms
64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=5 ttl=48 time=42.143 ms

If you get results from pinging by IP but not by name, you have a problem with your DNS servers.  If you cannot ping by name or IP, you havfe a problem with your gateway to the Internet or the Internet connection is down.

This works on all versions of SCO Xenix or SCO UNIX with networking.

Login as root and type ifconfig -a

net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.3 netmask ffffff00 broadcast 10.0.0.255
perf. params: recv size: 24576; send size: 24576; full-size frames: 1
ether 00:0c:29:f9:9c:ee
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
perf. params: recv size: 57344; send size: 57344; full-size frames: 1

The network card is identified by net0, net1, etc.  The loopback adapter is lo0.   The IP for this SCO UNIX server is 10.0.0.3.

Update the /etc/resolv.conf file and look for entries called nameserver.  Update these nameservers with the IP replacements.   Below is an example:

hostresorder local bind

nameserver 8.8.8.8

nameserver 4.2.2.3

This works on all versions of SCO UNIX.

The command lpstat -o will display any open print jobs.  Below is an example

laser5-11440                            root                33454              Au1 01 08:20

To cancel this print job type

cancel laser5-11440

This command works on SCO Xenix, and SCO Unix 5.02, 50.4, 5.05, 5.07, and SCO 6.0

Use the lpstat -t command to get the printer names

scheduler is running
system default destination: office
device for receipt2: /dev/ttya07
device for receipt1: /dev/ttya08
receipt2 accepting requests since Thu May 23 08:12:13 2013
receipt1 accepting requests since Fri May 31 11:08:02 2013
printer receipt2 is idle. enabled since Tue Mar 31 11:57:11 2015. available.
printer receipt1 is idle. enabled since Fri May 31 11:08:02 2013. available.

To disable the receipt1 printer type disable receipt1

Any print jobs sent to receipt1 will be held in the queue.

To enable the receipt1 printer type enable receipt1

This command works on SCO Xenix, and SCO Unix 5.02, 50.4, 5.05, 5.07, and SCO 6.0

In SCO OpenServer 5.0.7, the timezone may not display correctly which causes the time to be incorrect, even after you do:

scoadmin "System Time Manager" -> Time -> Change Timezone

To correct this, add the following line to /etc/profile:

. /etc/TIMEZONE 2>/dev/null

Now after a reboot, the date will show the correct timezone.

This works on SCO Xenix, SCO 5.05, 5.06, 5.07 and 6.0.

The Host version of SCO UNIX does not support networking with Ethernet cards and protocols such as TCP/IP.   Additional workstations on the HOST version of SCO UNIX only support the terminals connected using serial ports.

The Enterprise version of SCO UNIX support networking with Ethernet cards.  Workstations can connect to an Enterprise server using serial ports and TCP/IP.

This is valid on SCO UNIX 5.0, 5.2, 5.4, 5.6, 5.7 and 6.0.

uname -X will show the basic system information

System = SCO_SV
Node = ultimate
Release = 3.2v5.0.6
KernelID = 2000-07-27
Machine = >PentIII
BusType = ISA
Serial = 2AA00000
Users = 16-user
OEM# = 0
Origin# = 1
NumCPU = 1

The Node is the system name.   The release is 5.06 and the number of licensed users are 16. This command works on SCO Xenix, and SCO Unix 5.02, 50.4, 5.05, 5.07, and SCO 6.0.  SCO Xenix did not have a user limit so that would be omitted from this command.

The shutdown command will allow the user to specify the number of minutes before shutdown and to verify the shutdown when the countdown is complete.  Each minute before shutdown a broadcast is sent to all logged in users warning them the system is shutting down and to save their files and log off.  To start a shutdown with 5 minutes notice type.

#shutdown -g5

Broadcast Message from root (ttyp1) on ultimate Nov 15 05:27 2015...
The system will be shut down in 00:05
Please log off before shut-down.

To perform an immediate shutdown with no notice type  sync;sync;sync;haltsys

This command works on SCO Xenix, and SCO Unix 5.02, 50.4, 5.05, 5.07, and SCO 6.0

Add the commands to the /etc/profile file.  Example

. /etc/user.env

Suggestion:  Keep your login open and start another session to test.  You want to make sure you can login after your change.

faxsend phonenumber filename will get the job done

faxsend has a number of flags

-c             Don't generate a cover sheet

-l              Send job at low resolution

-t             Time to transmit

-p             Priority

-r              Tries - number of attempts to try

-h              Fax ID to transmit with job

-m             Mail Notification Level

0 = No Notification

1 = Always

2 = Only on error

-n               ASCII file of notes to attach to cover sheet

-H              Override system default page header for this job.

More options are available by typing faxsend and enter at the command line.  To send a fax with no cover sheet using a notes file of /tmp/notes type faxsend -c -n /tmp/notes 12489999999 /tmp/faxfile

This command works on Digifax version 2.9.0 on SCO Xenix and SCO UNIX.

The files received from Digifax can be converted to a tiff format so the user can view the received faxes on a Windows system.  To convert, run the following commands.  The faxclean program is provided as part of the Digifax program.  The fax2tiff command is included with the gwxlibs update on the Skunkware directory of http://sco.com/skunkware

cd /usr/spool/fax/rx

faxclean incoming.fax temp.fax

fax2tiff temp.fax temp.tif

This can be embedded into a script to convert all your Digifax faxes, renumber them and move to a share the user can view to a Windows system.
This command works on Digifax version 2.9.0 which runs on SCO Xenix and SCO UNIX.

Get a listing of faxes int the queue using the faxstat command

faxstat

To delete the job 77090 type faxsend -d 77090.  Only that user can delete a fax job.   If you are root you can su - john first and delete the job.

This command works on Digifax version 2.9.0 which runs on SCO Xenix and SCO UNIX.