8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Guys i have one file and i want the o/p from that file like below
This is my sample file and i want below things from it.
Name:
Sate just below the name:
And retention Level
Name: MEANS_SLP_DAILY
State: inactive
Retention Level: 3... (6 Replies)
Discussion started by: nirjhar17
6 Replies
2. Shell Programming and Scripting
Guys i have one file and i want the o/p from that file like below
This is my sample file and i want three things from it.
Name:
State just below the Name: dont want the state under the Retention Level:
And retention Level
Name: MEANS_SLP_DAILY
State:... (1 Reply)
Discussion started by: nirjhar17
1 Replies
3. Shell Programming and Scripting
I'm relatively new to both UNIX and Linux and slightly less new at programming. But I can't figure out why this won't run properly.
It's meant to calculate the GCD of two numbers (simple enough, you'd think). And I designed it myself and it looks good to me and my instructor won't respond. If... (1 Reply)
Discussion started by: Sevchenko
1 Replies
4. Shell Programming and Scripting
Now theres another problem. I would like to output not just a colored block, but how would I output not a solid block character, but a shaded block instead?
Please help. I'm writing a library for these codes and this would really help. (4 Replies)
Discussion started by: tinman47
4 Replies
5. Shell Programming and Scripting
Hi I am working with a 3.0 GB file and running the following script to process it. After running for 15 minutes, the script stops saying Out of memory or Killed.
Can the experts suggest where my code can be improved to save memory?
Thanks in advance.
#! usr/bin/perl
use warnings;
open... (3 Replies)
Discussion started by: polsum
3 Replies
6. Windows & DOS: Issues & Discussions
Hello everyone. I just recently installed Cygwin and I am running it under Windows 7.
My problem is that I cannot seem to compile any C++ code with g++. I've tried to compile C Code using gcc and that works just fine. But Whenever I try to compile some C++ code, g++ throws a whole bunch of... (6 Replies)
Discussion started by: Anlex
6 Replies
7. Shell Programming and Scripting
Hello
I am trying to write a script that sends files via ftp from one server to another, i am using AIX 5.1. and bash shell to write my code.
I get an error when trying to run the following lines of code
ftp -n aptsbou01 <<!
user $username $password
binary
... (4 Replies)
Discussion started by: kswaraj
4 Replies
8. Programming
This code is not working properly because it dont open the requested file. I am not able to find out what the error is?? can anyone fix the error for me??
#include <sys/types.h>
#include <sys/wait.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include... (2 Replies)
Discussion started by: badshah
2 Replies
stl_key(4) Kernel Interfaces Manual stl_key(4)
NAME
stl_key - setld kit manufacturing key files
DESCRIPTION
Each software product that is distributed as subsets for the setld(8) command has an associated key file. The key file's name consists of
the product's unique 3-letter name and a 3-digit version number with the string .k for a suffix. The key file is used by the software kit-
ting program kits(1) in producing software distribution packages.
A key file has a global data section and a subset descriptor section. The sections are separated by a line containing only two percent
signs (%%).
The global section specifies the product-level attributes of the product. In this section, lines that begin with number signs (#) are com-
ments and are ignored by the kits utility. Attributes are specified as name/value pairs separated by equals signs (=). There must be no
white space surrounding the equals sign. There are four mandatory attributes and two optional attributes. Attributes must have non-null
values. The attributes are:
NAME Mandatory. Specifies the name of the product. The value for NAME is a text string of up to 40 characters. If the string con-
tains blank spaces, it must be enclosed in apostrophes ('').
CODE Mandatory. Specifies the 3-character product code for the product, for example, OAT.
VERS Mandatory. Specifies the 3-digit version code for the product, for example, 100.
MI Mandatory. Specifies the pathname of the master inventory file for the product.
ROOT Optional. A single-digit integer that is set to 1 if the product is the base operating system. In all other cases, this flag
must be a zero (0). If missing, this attribute defaults to zero.
COMPRESS Optional. A single-digit integer that is set to 1 to create compressed subset files using the compress(1) utility, thereby sav-
ing space on the distribution media. To suppress compression, this attribute is a zero (0). If missing, this attribute defaults
to zero.
The subset descriptor section contains one subset descriptor line for each subset in the product. Comments are not permitted in this sec-
tion.
A subset descriptor contains subset-specific attributes in four fields separated by TAB characters. These fields are:
Subset name A character string up to 15 characters in length, composed of the 3-letter product code (for example, OAT), a mnemonic iden-
tifying the subset (for example, DCB), and the 3-digit version code (for example, 100). All letters in the subset name must
be uppercase.
Reserved This field must be a single period.
Flags A 16-bit unsigned integer
Bit 0 is the ``sticky bit,'' indicating when set that the subset cannot be removed.
Bit 1 indicates when set that the subset is optional.
Bits 2 to 7 are reserved.
Bits 8 to 15 are undefined.
Description A short description of the subset, delimited by single quotation marks (''); for example, 'Document Building Tools'
The subset descriptors must be listed in the order in which the subsets are to be installed by setld.
RESTRICTIONS
Comments in the subset descriptor section will cause serious problems when encountered by the kits program.
TAB formatting in the subset descriptors is tightly enforced by the kits program.
EXAMPLES
The following example illustrates the key file for a hypothetical product kit: # Key file for the Orpheus Document Building Tools kit
# # Product-level attributes. # NAME='Orpheus Authoring Tools' CODE=OAT VERS=100 MI=OAT00.mi ROOT=0 COMPRESS=1 # # Subset def-
initions follow. # %% OATDCB100 . 0 'Document Building Tools' OATDCBDOC100 . 2 'Document Tools Documenta-
tion'
RELATED INFORMATION
Commands: kits(1), setld(8)
Files: stl_comp(4), stl_ctrl(4), stl_image(4), stl_mi(4)
Documents: Guide to Preparing Product Kits delim off
stl_key(4)