Differences between revisions 4 and 5
Revision 4 as of 2018-10-21 23:52:26
Size: 6626
Editor: fuzzy
Comment:
Revision 5 as of 2018-10-22 01:30:59
Size: 6785
Editor: fuzzy
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
<insert screen cap of company file maintenance here>

Don't forget to delete your link

{{{
Line 32: Line 37:


}}}
Then go to your company:

{{{
conset -c <COMPANYNAME>
}}}

Copy CONTROL

Rsync from sam to ccstandard (add this to OS install instructions)

on the new machine

mkdir /u/ccr.<release_no>
cd /u/ccr.<release_no>
rsync -av /u/ccstandard/ ./

Create a new environment:

mkdir /u/cc<companyname>
cd /u/cc<companyname>
rsync -av /u/ccr.<release_no>/{adm,binl,binx11,LOG,overlay,usr} ./
ln -s /u/ccr.<release_no>/{env,lang_ts,lib,manual,pixmap,standard,std} ./

Set up a new company

export CCDIR=/u/cc<companyname>
export NODEID=vnc:5
cp -a standard <COMPANYNAME>
cd
ln -s `which coaad` contrl
./contrl

Clone the "standard" company to <COMPANYNAME> (make sure COMPANYNAME is in all caps, and 8 characters or less)

<insert screen cap of company file maintenance here>

Don't forget to delete your link

rm ./contrl

Then go to your company:

conset -c <COMPANYNAME>


Package control programs on sam (Server side)

export
_FILES="
std/binl
std/utbinl
std/binx11
std/utbinx11
adm
blank
standard
standard.adm
pixmap
lib
binl
binx11
DEMO
manual
usr/common.linux
"
cd /u/ccdev/
tar cvzhf
.tgz --exclude=.sccs $
_FILES

send control.tgz to client machine

Setup /u/cc/ directory (Client Side)

touch /dev/lp8
chmod 666 /dev/lp8
umask 0
mkdir /u/cc/
chmod 777 /u/cc/
ln -s /u/cc /cc
mkdir /u/cc/usr
chmod 777 /u/cc/usr
ln -s ~ccc /u/cc/usr/ccc
mkdir /u/cc/LOG
chmod 777 /u/cc/LOG
chown ccc:
 /u/cc/LOG /u/cc/usr
chown ccc:
 /u/cc/usr/ccc /u/cc/usr/ccc/.*
cd /u/cc
tar xvzf PATH_TO_
_TAR_FILE/
.tgz (do this step if you have already copied
.tgz to client machine)
chown ccc:
 std/* std/*/*
chown ccc:
 binl/*
chown ccc:
 binx11/*
binl/link_cntrl
chown ccc:
 standard/*
chmod 666 standard/*
cp /u/cc/standard.adm/* /u/cc/adm
mv /u/cc/usr/common.linux /u/cc/usr/common.sh

Libraries

For Fedora versions prior to Fedora Core 5, update /etc/ld.so.conf to included the following line

/u/cc/lib

For Fedora Core 5 and later, execute:

cd /usr/lib
ln -s /u/cc/lib/libcqt3.* .

You will also need to edit /u/cc/usr/common.sh

LD_LIBRARY_PATH=/lib:/usr/lib:$CCDIR/lib

Then for all versions to rebuild the library cache execute:

ldconfig

Install necessary fonts

As a minimum, the system should have the 75-dpi, 100-dpi and truetype fonts appropriate for the installed X Font Server

To search for the fonts:

yum search fonts

The packages are usually of the form fonts-xorg-75dpi

Once you have found the correct fonts packages

yum install <font package>

Make console (DISPLAY=0) a VNC server

Edit /etc/X11/xorg.conf

Section "Module"
        Load "vnc"      # Add this line
EndSection
Section "Screen"
        Option "PasswordFile" "/u/cc/usr/ccc/.vnc/passwd"       # Add this line
EndSection

Installing FVWM

We use FVWM as a slimline window manager where users don't need or expect a full remote desktop. You'll need to locate files fvwm-2.4.19-1.i386.rpm and libstroke-0.5.1-4.fc4.i386.rpm which are available on sam.

# yum install compat-readline43 gtk+ imlib
# rpm -Uvh fvwm-2.4.19-1.i386.rpm fvwm-themes-0.6.2-1.noarch.rpm libstroke-0.5.1-4.fc4.i386.rpm

Need to update Xclients such that FVWM is started when local user logs in.

# cd /etc/X11/xinit
# mv Xclients Xclients.bak
# vi Xclients

Update Xclients to initialise the control environment and execute FVWM as below:

rm -f $HOME/Xrootenv.0
rm -f /tmp/fvwmrc* 2>/dev/null
. /u/cc/usr/common.sh
exec /usr/bin/fvwm

Finally give Xclients execute permissions

chmod +x Xclients

Configuring FVWM

mkdir /etc/X11/fvwm2

Copy from system.fvwm2rc from /u (sam) or from a recent client's system and place it in the newly created directory. Also place a symbolic link to system.fvwm2rc in /etc/

ln -s /etc/X11/fvwm2/system.fvwm2rc /etc/

User Manuals

Install Firefox

yum install firefox

Download the Adobe Acrobat Reader plugin at http://www.adobe.com and install

firefox http://www.adobe.com

User manual files already included in the tarball copied from sam (/u/ccdev/manual)

Post Control Installation Options

Backups

  • cocont option Days before display system warning mesg should be set to 30. This allows the client to have at least one system backup to restore various configuration system configuration files in the event of a failure.

  • Enter the Linux device into cocont's Backup device field.

Scheduled processes

Enter the company code in the script /cc/binl/clrdayqty . crontabsetup auto_postal, eom_job, initda/backups and other scripts that need to run automatically.

For ccc:

* * * * * /u/cc/binl/auto_postal 2>&1 > /u/cc/LOG/auto_postal.out
1 0 1 * * /u/cc/binl/auto_eom >/u/cc/LOG/auto_eom 2>&1
59 23 * * * /u/cc/binl/auto_signoff > /u/cc/LOG/auto_signoff 2>&1
10 0 * * * /u/cc/binl/post_sum > /u/cc/LOG/post_sum 2>&1
0 22 * * * /cc/binl/clrdayqty > /cc/LOG/clrdayqty.out 2>&1

For root:

30 2 * * * /u/cc/binl/netchecktime > /u/cc/LOG/netchecktime.out 2>&1
# The daily backup script
0 3 * * * /u/cc/binl/bacint -s > /u/cc/LOG/bacint.out 2>&1
# Initialise dayfile. Only needed if not using our backup script
#0 3 * * * /u/cc/binl/initda -s > /u/cc/LOG/initda.out 2>&1

Background tasks

You will need to edit /etc/inittab:

id:5:initdefault:  # Need to change run level from 3 to 5
v5:345:respawn:su - ccc -c /usr/local/bin/inittab_vnc 2>&1 >> /var/log/vnc.ccc

Customer Company

  • coaad Setup the company record(s) for the customer.

  • Ensure that the /u/cc/<CUSTOMER> directory exists and is a copy of standard. Also make sure that the correct amount of users and locations have been set.

  • Enter the customer's company name into cocont's Company codes to be backed up field.

Printers, Overlays and Docket Logos

You will need to get the customer's logo and artwork from the sales team.

To create a docket logo, see Docket_Logo.

For a list of compatible laser printers, seeLaser_Printers.

For setting up printers, see InstallingPrinter.

Data Imports

  • Run any data imports necessary.

Setting up a DEMO company in a server

Follow DemoCD under Linux steps 1-14 for the DEMO company and additional companies as needed.

Describe Installing_Control here.

Installing_Control (last edited 2019-03-11 05:08:01 by fuzzy)