DOCSLIB.ORG

Log File Management Tool Deployment and User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Log File Management Tool Deployment and User's Guide Log File Management Tool Deployment and User's Guide Deployment of SSH and RSYNC 9/24/2021 Contents • 1 Deployment of SSH and RSYNC • 1.1 On Linux • 1.2 On Windows • 1.3 Important Notes Log File Management Tool Deployment and User's Guide 2 Deployment of SSH and RSYNC Deployment of SSH and RSYNC SSH is a secure protocol used to connect two computers over a given network. RSYNC is a highly efficient file transfer mechanism. LFMT leverages RSYNC over SSH connections to copy log files from an application server host to the LFMT Server Host(s). LFMT requires that all hosts to which LFMT will collect log files have both SSH and RSYNC installed. Likewise, SSH and RSYNC is also required on the LFMT Server Host(s). This section describes how to deploy and configure SSH and RSYNC on all hosts in a LFMT deployment. Tip Genesys strongly recommends that you use an Administrator account when installing and configuring the following components. This user should be specified under the LFMT Collector option unix_user_account for Linux/UNIX environments, or the windows_user_account for Windows environments. For mixed environments, both options should be set accordingly. On Linux Installing SSH on a Linux host Purpose: Use this procedure to install SSH on all Linux hosts. 1. Download OpenSSH from the following URL: http://www.openssh.org/ 2. From the Linux command line, enter the following command and press Enter: yum -y install openssh-server openssh-clients 3. To start and enable the sshd server, enter the following commands, pressing Enter after each: chkconfig sshd on service sshd start 4. To open port 22 over which all IP addresses will communicate with RSYNC and the LFMT, enter the following commands, pressing Enter after each: /sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT service iptables save Log File Management Tool Deployment and User's Guide 3 Deployment of SSH and RSYNC Installing RSYNC on a Linux host Purpose: Use this procedure to install RSYNC on all Linux hosts. 1. Ensure OpenSSH has been installed on the application server host. 2. On the command line, enter one of the following commands, depending on your Linux operating system: a. On Ubuntu systems yum install rsync b. On Red Hat Enterprise Linux and CentOS systems yum -y install rsync 3. Press Enter. Distributing public keys for LFMT access to remote hosts Purpose: Use this procedure to create and distribute public encryption keys for securing log file transfer between the LFMT Server Host(s) and the application server hosts. 1. On the command line, enter the following commands, and press Enter after each: yum install tcl yum install expect Important The tcl package is included in RHEL, CentOS and Ubuntu. The expect package is part of tcl. 2. Open (or create, if necessary) the keys_conf.txt file in the text editor. (A sample copy is located under the <LFMT Collector Install Directory>/utilities directory.) 3. Enter all the information about each application server host (host name, user name, password), one server per line with information fields separated by a tab character, as follows: <host><tab><username><tab><password> For example, the following is a keys_conf.txt file for three application server hosts: ca-to-alum genesysWIN password ca-to-bond genesysWIN password ca-to-port genesysLNX password Log File Management Tool Deployment and User's Guide 4 Deployment of SSH and RSYNC Important Passwords must not contain the following special characters: (){}[]'"\/$ The value for username given in the keys_conf.txt file is case-sensitive. The case of this value should reflect that which is configured on the domain controller. To ensure the proper case, the following command can be run from the terminal window to query the domain controller: mkpasswd -d -u <username> The above command will produce an output similar to that below: <username>:unused:77777:11111:<User Name>,U-<DOMAIN>\<username>,S-1-8-21-2222222222-965789356-1112345605-55555:/home/<username>:/bin/bash The case used for defining username should reflect the first instance of its occurrence in the above output. The same case for username should be used when defining unix_user_account or windows_user_account in the LFMT Collector configuration options. 4. Save the file. 5. Ensure that the <LFMT Collector Install Directory>/lfm_keys.sh file is in the same directory as the keys_conf.txt file. 6. Open a Linux terminal and navigate to the directory where the lfm_keys.sh file is stored. 7. Execute the script: ./lfm_keys.sh The time taken for this script to execute depends on the number of application server hosts defined in the keys_conf.txt file. Tip Because it contains user names and passwords, you may want to delete the keys_conf.txt file or move it to a secure location after using it to configure LFMT. You will need to edit or recreate this file anytime you want to add new application servers to LFMT log collection. On Windows Installing SSH and RSYNC on a Windows host Purpose: On Windows, SSH and RSYNC are available via a Linux emulator named Cygwin. Use this procedure to install Cygwin on a Windows host. Log File Management Tool Deployment and User's Guide 5 Deployment of SSH and RSYNC 1. Locate and extract the cygwin.zip file that is found in the <LFMT Collector Install Directory>\utilities directory. 2. From the location where the cygwin.zip file was extracted, run the setup.exe file from the Cygwin Setup File folder. 3. Select Install from Local Directory. 4. Set the following parameters: a. Set the root directory to the path where Cygwin is to be installed. b. Select Install for All Users. c. In the Local Package Directory field, specify the path to the Cygwin local directory folder found in the location where the cygwin.zip file was extracted. d. Click Next. 5. Select the following packages to install. a. From Admin, select all of the packages. b. From Archive, select the unzip and zip packages. c. From Editors, select the vim package. d. From Net, select the openssh, rsync, and tcp_wrappers packages. e. From Tcl, select expect package. 6. Click Next to install the packages. 7. On the Installation Complete screen, click Finish. 8. Add values to the Environment PATH variable, as follows: a. Right-click on the My Computer icon on your desktop and select Properties from the drop-down menu. b. Open the Advanced tab and click Environment Variables. c. Create a new system variable, CYGWIN_HOME, and set the value to the directory where the Cygwin folder is stored. For example, name=CYGWIN_HOME, value=C:\Cygwin. Click OK. d. Scroll through the System variables list, and select PATH, then click Edit. e. Add %CYGWIN_HOME%\bin to the existing parameters. Make sure that the %CYGWIN_HOME%\bin is set AFTER the path to PERL lib folder. f. Click OK twice more to close the System Properties dialog box. Configuring SSH for LFMT on a Windows host Purpose: Use this procedure to configure SSH for LFMT on a Windows host. 1. Right-click on the Cygwin terminal icon and select “Run as administrator”. 2. Navigate to the directory containing the cygwin_setup.sh file. Log File Management Tool Deployment and User's Guide 6 Deployment of SSH and RSYNC 3. Convert the cygwin_setup.sh file to the Unix text format. Enter: dos2unix cygwin_setup.sh 4. Configure the SSH service. Enter: bash cygwin_setup.sh <username> "<password>" 5. Copy cygwin_setup.sh and cygrun.bat files under <LFMT Collector Install Directory>\utilities to the root folder of the Cygwin installation. Important Passwords must not contain the following special characters: (){}[]'"\/$ The screenshot below shows the messages received during a successful deployment of the SSH service. Log File Management Tool Deployment and User's Guide 7 Deployment of SSH and RSYNC Log File Management Tool Deployment and User's Guide 8 Deployment of SSH and RSYNC Installing and configuring SSH and RSYNC on a Windows host (Mass Deployment) Purpose: On Windows, SSH and RSYNC are available via a Linux emulator named Cygwin. Use this procedure to mass deploy Cygwin from a Windows host to all other Windows hosts. 1. Install and configure SSH and RSYNC on at least one Windows host via the steps above. This is the primary Windows host. 2. Ensure WMIC is installed on the application server host, and the Windows firewall is configured to allow a WMIC connection. To test that WMIC is working properly on the application server host, go to http://wiki.serverscheck.com/ index.php/Testing_wmi. 3. Ensure all hosts to which Cygwin is being deployed have hostnames that can be resolved from the primary Windows host. 4. Locate and extract the cygwin.zip file that is found in the <LFMT Collector Install Directory>\utilities directory. 5. Create a new network shared folder from the extracted cygwin.zip file. 6. Open (or create, if necessary) the cygwin_conf.txt file (a sample copy is located under found under <LFMT Collector Install directory>\utilities) in the text editor. 7. Enter in this file all information about each application server host (computer name, domain, username, password), one server per line, with information fields separated by a tab character. The format of each line is as follows: <host><tab><domain><tab><primary drive><tab><username><tab><password> For example, the following is a cygwin_conf.txt file for three application server hosts: ca-to-alum Genesys C: genesysWIN password ca-to-bond Genesys L: genesysWIN password ca-to-west Genesys I: genesysWIN password The values for domain and username given in the cygwin_conf.txt file are case-sensitive. The case of these values should reflect that which is configured on the domain controller.
Load more

Recommended publications
  • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc
    • • • • • • Ajuba Solutions Version 1.4 COPYRIGHT Copyright © 1998-2000 Ajuba Solutions Inc. All rights reserved. Information in this document is subject to change without notice. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic or mechanical, including but not limited to photocopying or recording, for any purpose other than the purchaser’s personal use, without the express written permission of Ajuba Solutions Inc. Ajuba Solutions Inc. 2593 Coast Avenue Mountain View, CA 94043 U.S.A http://www.ajubasolutions.com TRADEMARKS TclPro and Ajuba Solutions are trademarks of Ajuba Solutions Inc. Other products and company names not owned by Ajuba Solutions Inc. that appear in this manual may be trademarks of their respective owners. ACKNOWLEDGEMENTS Michael McLennan is the primary developer of [incr Tcl] and [incr Tk]. Jim Ingham and Lee Bernhard handled the Macintosh and Windows ports of [incr Tcl] and [incr Tk]. Mark Ulferts is the primary developer of [incr Widgets], with other contributions from Sue Yockey, John Sigler, Bill Scott, Alfredo Jahn, Bret Schuhmacher, Tako Schotanus, and Kris Raney. Mark Diekhans and Karl Lehenbauer are the primary developers of Extended Tcl (TclX). Don Libes is the primary developer of Expect. TclPro Wrapper incorporates compression code from the Info-ZIP group. There are no extra charges or costs in TclPro due to the use of this code, and the original compression sources are freely available from http://www.cdrom.com/pub/infozip or ftp://ftp.cdrom.com/pub/infozip. NOTE: TclPro is packaged on this CD using Info-ZIP’s compression utility.
    [Show full text]
  • ARM Code Development in Windows
    ARM Code Development in Windows By: Ali Nuhi This guide will describe how to develop code to be run on an embedded Linux system using an ARM processor (specifically the OMAP3530). Environment The Cygwin bash shell will be the environment used for code development. Download it from the below link. http://cygwin.com/install.html READ THE SITE. Download setup.exe and choose the packages you want to install. Some helpful packages to download are: -gcc4-core,g++ etc. (for c and c++ compiling of normal programs) -git core files and completion (version control system) -wget (utility to download files from the internet via HTTP and FTP) -VIM (text editor) -Xemacs (another text editor, better than vim) -nano (simple command line text editor) If you still use windows notepad for writing code please atleast upgrade to notepad++. Toolchain We will be compiling and creating files using CodeSourcery g++ lite toolchains. This is a modified version of GCC which will create files specifically for ARM target systems. Download this at: http://www.codesourcery.com/sgpp/lite/arm/portal/release1803 Download the Windows installer and execute. You can let it install as is unless you have some other install scheme on your computer. I highly recommend reading the getting started pdf that comes with CodeSourcery. Once it’s fully installed open up Cygwin and execute the below lines. $ export CYGPATH=cygpath $ export CYGPATH=c:/cygwin/bin/cygpath If you installed Cygwin to another directory then you must edit the second line. To use the compiler type the following and hit tab twice to see all of the possible options you have.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Scripting: Higher- Level Programming for the 21St Century
    . John K. Ousterhout Sun Microsystems Laboratories Scripting: Higher- Cybersquare Level Programming for the 21st Century Increases in computer speed and changes in the application mix are making scripting languages more and more important for the applications of the future. Scripting languages differ from system programming languages in that they are designed for “gluing” applications together. They use typeless approaches to achieve a higher level of programming and more rapid application development than system programming languages. or the past 15 years, a fundamental change has been ated with system programming languages and glued Foccurring in the way people write computer programs. together with scripting languages. However, several The change is a transition from system programming recent trends, such as faster machines, better script- languages such as C or C++ to scripting languages such ing languages, the increasing importance of graphical as Perl or Tcl. Although many people are participat- user interfaces (GUIs) and component architectures, ing in the change, few realize that the change is occur- and the growth of the Internet, have greatly expanded ring and even fewer know why it is happening. This the applicability of scripting languages. These trends article explains why scripting languages will handle will continue over the next decade, with more and many of the programming tasks in the next century more new applications written entirely in scripting better than system programming languages. languages and system programming
    [Show full text]
  • Ixia Tcl Development Guide
    Chapter 2: Quick Start 2 Installing the IxOS Tcl Client This chapter provides a quick means of getting started with the Tcl API. An example test is presented and explained. The IxOS Tcl Client provides an interface between an Ixia Tcl client application and Ixia IxOS Tcl functions. It runs on the Unix / Linux host. The Windows version of IxOS Tcl Client is included with the IxOS software package; the Unix/Linux version is supplied as a separate a self-extracting archive (.bin) file. You can download it from Ixia’s website, www.ixiacom.com. There are serveral versions of the IxOS Tcl Client. The correct file to install depends on the set up of the UNIX/Linux machine. Table 2-2 on page 2-1 details the files and their use. Table 2-2. Tcl Client Install Files Install File Purpose IxOS#.## For Linux versions post Redhat 9. It is distributed as genericLinux.bin a tarball (IxOS#.##genericLinux.bin.tar.gz) due to download issues. IxOS#.##linux.bin. For Linux platforms older than Redhat 9. IxOS#.##setup.jar An installer without a bundled Java Virtual Machine. This is distributed only to customers that have issues running the bin installers. It requires a Java Virtual Machine installed on the installation target. IxOS#.## For Solaris machines. solarisSparc.bin The versions of UNIX/Linux operating systems that are supported are: • Mandrake 7.2, RedHat 6.2, RedHat 7.0, RedHat 9.0 • RedHat Enterprise 4.0 IxOS Tcl Development Guide, 6.60 EA SP1 2-1 Quick Start 2 Installing the IxOS Tcl Client • Solaris 2.7 (7), 2.8 (8), 2.9 (9) Other versions of Linux and Solaris platforms may operate properly, but are not officially supported.
    [Show full text]
  • Automating Your Sync Testing
    APPLICATION NOTE By automating system verification and conformance testing to ITU-T synchronization standards, you’ll save on time and resources, and avoid potential test execution errors. This application note describes how you can use the Paragon-X’s Script Recorder to easily record Tcl, PERL and Python commands that can be integrated into your own test scripts for fast and efficient automated testing. AUTOMATING YOUR SYNC TESTING calnexsol.com Easily automate synchronization testing using the Paragon-X Fast and easy automation by Supports the key test languages Pre-prepared G.8262 Conformance recording GUI key presses Tcl, PERL and Python Scripts reduces test execution errors <Tcl> <PERL> <python> If you perform System Verification language you want to record i.e. Tcl, PERL SyncE CONFORMANCE TEST and Conformance Testing to ITU-T or Python, then select Start. synchronization standards on a regular Calnex provides Conformance Test Scripts basis, you’ll know that manual operation to ITU-T G.8262 for SyncE conformance of these tests can be time consuming, testing using the Paragon-X. These tedious and prone to operator error — as test scripts can also be easily tailored well as tying up much needed resources. and edited to meet your exact test Automation is the answer but very often requirements. This provides an easy means a lack of time and resource means it of getting your test automation up and remains on the ‘To do’ list. Now, with running and providing a repeatable means Calnex’s new Script Recorder feature, you of proving performance, primarily for ITU-T can get your automation up and running standards conformance.
    [Show full text]
  • CS102: Introduction to Python the Goal of This Topic Is to Provide a Brief
    CS102: Introduction to Python The goal of this topic is to provide a brief introduction to Python to give you a feel for a language other than C. In many ways, Python is very different from C. It is generally considered to be a scripting language, although the distinction between scripting languages and other programming languages is not really clear-cut. Scripting languages tend to be interpreted rather than compiled; they tend not to require declarations of variables (the interpreter figures out types based on context); they tend to hide memory management from the programmer; they tend to support regular expressions; etc. In terms of usage, scripting languages tend to be useful for writing short programs quickly when you don't care too much about efficiency. Other languages that are typically considered to be scripting languages include Perl, Awk, and JavaScript. Python supports several styles of programming, including (but not limited to) procedural programming (like C and C++), object-oriented programming (like C++ and Java), and functional programming (like Lisp). Note that it is not a mistake to include C++ in two categories, just as it is not a mistake to include Python in all three of these categories. The first version of Python was released in the late 1980s. Python 2.0 was released in 2000, and various improvements have been made in the Python 2.x chain of releases since that time. Python 3.0 was released in 2008, and again, various improvements have been made in the Python 3.0 chain of releases. Unfortunately, the Python 3 interpreter is not backwards compatible with Python 2, and there seems to be debate as to which is the better version of Python to learn.
    [Show full text]
  • Installing & Using Cygwin/X
    Installing & Using Cygwin/X Arnon Erba Agricultural & Resource Economics Updated October 24, 2019 Contents 1 Installation 2 1.1 Downloading Cygwin...................................2 1.2 Installing Cygwin.....................................2 2 Usage 3 2.1 Launching the X Server.................................3 2.1.1 Method 1: From Start Menu (Recommended).................3 2.1.2 Method 2: From Cygwin Terminal.......................4 2.2 Opening a Terminal Window...............................4 2.3 Closing the X Server...................................5 3 Troubleshooting6 3.1 Can't read lock file....................................6 3.2 Stdin is not a terminal..................................6 1 Abstract Cygwin is an open-source POSIX-compatible environment for Windows that offers many useful GNU/Linux utilities including an X server. Cygwin's X server allows apps requiring the X Window System to run on Windows. When paired with a suitable SSH client, the Cygwin X server can be used to run graphical (GUI) applications on remote servers over SSH. Though Cygwin offers a large number of packages, only a few are required for Cygwin/X. 1 Installation 1.1 Downloading Cygwin Download the Cygwin installer from www.cygwin.com. The installer is named setup-x86 64.exe. Note: If desired, the original installer can be re-run to add additional packages after installation is complete. 1.2 Installing Cygwin 1. Run the downloaded .exe file and follow the prompts. The default options are recommended, such as: • Install from Internet • Root Directory: C:ncygwin64 • Install For: All Users 2. Choose a download site from the list when prompted. Sites that appear to be US-based may offer faster download times due to geographical proximity.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide i Cygwin User’s Guide Cygwin User’s Guide ii Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Red Hat, Inc. Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .5 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select .
    [Show full text]
  • Debug Malloc Library Version Version 5.6.5 December 2020
    Debug Malloc Library Version Version 5.6.5 December 2020 Gray Watson This manual is licensed by Gray Watson under the Creative Commons Attribution-Share Alike 3.0 License. Permission is granted to make and distribute verbatim copies of this manual provided this license notice and this permission notice are preserved on all copies. i Table of Contents Debug Malloc Library ......................... 1 1 Library License and Copying Information ... 2 2 Description of Features and How to Get Started .................................. 3 2.1 How to Install the Library ............................... 3 2.2 Getting Started with the Library ......................... 4 2.3 Basic Description of Terms and Functions ................. 6 2.3.1 General Memory Terms and Concepts ............ 6 2.3.2 Functionality Supported by All Malloc Libraries .. 7 2.4 General Features of the Library .......................... 8 2.5 How the Library Checks Your Program .................. 10 3 How to Program with the Library ......... 12 3.1 Macros Providing File and Line Information.............. 12 3.2 Getting Caller Address Information...................... 12 3.3 Checking of Function Arguments ........................ 13 3.4 Generating a Core File on Errors ........................ 13 3.5 Additional Non-standard Routines....................... 14 3.6 Description of the Internal Error Codes .................. 18 3.7 How to Disable the library .............................. 21 3.8 Using the Library with C++ ............................. 22 3.9 Using Dmalloc With a Debugger ........................ 22 3.9.1 Diagnosing General Problems with a Debugger... 23 3.9.2 Tracking Down Non-Freed Memory ............. 23 3.9.3 Diagnosing Fence-Post Overwritten Memory ..... 24 3.9.4 Translating Return Addresses into Code Locations ................................................ 25 3.10 Using the Library with a Thread Package ..............
    [Show full text]
  • 13A04806 LINUX PROGRAMMING and SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Struct
    13A04806 LINUX PROGRAMMING AND SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Structures ,Control Flow Commands, Procedures and Scope , Evel, Working With UNIX, Reflection and Debugging, Script Libraries, Tk Fundamentals ,Tk by Examples, The Pack Geometry Manager, Binding Commands to X Events, Buttons and Menus, Simple Tk Widgets, Entry and Listbox Widgets Focus, Grabs and Dialogs 13A04806 LINUX PROGRAMMING AND SCRIPTING Tcl - Overview Tcl is shortened form of Tool Command Language. John Ousterhout of the University of California, Berkeley, designed it. It is a combination of a scripting language and its own interpreter that gets embedded to the application, we develop with it. Tcl was developed initially for Unix. It was then ported to Windows, DOS, OS/2, and Mac OSX. Tcl is much similar to other unix shell languages like Bourne Shell (Sh), the C Shell (csh), the Korn Shell (sh), and Perl. It aims at providing ability for programs to interact with other programs and also for acting as an embeddable interpreter. Even though, the original aim was to enable programs to interact, you can find full-fledged applications written in Tcl/Tk. Features of Tcl The features of Tcl are as follows − ∑ Reduced development time. ∑ Powerful and simple user interface kit with integration of TK. ∑ Write once, run anywhere. It runs on Windows, Mac OS X, and almost on every Unix platform. ∑ Quite easy to get started for experienced programmers; since, the language is so simple that they can learn Tcl in a few hours or days. ∑ You can easily extend existing applications with Tcl.
    [Show full text]
  • 7 Reasons the Future of Tcl Is Bright by Clif Flynt ([email protected]) 7 Reasons the Future of Tcl Is Bright
    7 REASONS THE FUTURE OF TCL IS BRIGHT BY CLIF FLYNT ([email protected]) 7 REASONS THE FUTURE OF TCL IS BRIGHT The future is bright for Tcl! You’d be pardoned for his repertoire. He started shell programming in 1985, thinking otherwise. It’s not a sexy new language. In fact, picked up Perl in 1995 and finally Tcl in 1996. He’s been a it’s ranked outside the Top 50 in the TIOBE Index1. Tcl devotee ever since. But for the right projects - and there are lots of them - it’s With Clif’s extensive background, we asked him about a powerful tool that’s been stress-tested for many years the future of Tcl. Here’s seven reasons why the future and just gets the job done. of Tcl is bright. Tcl is not resting on its laurels. The simplicity of the Tcl language makes it perfect for Internet of Things IoT and 1: TCL IS STILL THE KING OF electronics design, including Electronic Design Automa- RAPID PROTOTYPING tion (EDA), chip design, and Field-Programmable Gate Clif is a big fan of Tcl for rapid prototypes that actually Array (FPGA) development, and for configuring chips after work. NBC Broadcasting studios uses Tcl/Tk to control manufacture. The same features that make Tcl dominant what you see. They went to GE Research (and others) in EDA and FPGA also make it great for DevOps, poten- with a half-baked design and some examples of the tially competing with Bash and Perl as the language of clipboards and tapes they were using.
    [Show full text]