My input:
File_1:
2000_t
g1110.b1
abb.1
2001_t
g1111.b1
abb.2
abb.2
g1112.b1
abb.3
2002_t
.
.
File_2:
2000_t Ali england 135
abb.1 Zoe british 150
2001_t Ali england 305
g1111.b1 Lucy russia 126 (6 Replies)
My file looks like this:
But I would like to 'trim' all sequences to the same lenght 32 characters, keeping intact all the identifier (>GHXCZCC01AJ8CJ)
Would it be possible to use awk to perform this task? (2 Replies)
My file looks like this
But I need to remove the entry with the identifier >Reference1 along with the entire sequence. Thus, I will end up having the following file
Thanks in advance! (2 Replies)
My file looks something like this
Wnat I need is to look for the Reference sequence (">Reference1") and based on the length of that sequence trim all the entries in that file. So, the rersulting file will contain all sequences with the same length, like this
Thus, all sequences will keep... (5 Replies)
Hi Unix gurus,
I am trying to remove the filenames based on MMDDYYYY in the physical name as such so that the directory always has the recent 3 files based on MMDDYYYY. "HHMM" is just dummy in this case. You wont have two files with different HHMM on the same day.
For example in a... (4 Replies)
Hi,
I have a string say "whateverCluster".
I need everthing apart from the string "Cluster"
Input:
whateverCluster
Desired output:
whatever (5 Replies)
Hi,
I have a file with more than 28000 records and it looks like below..
>mm10_refflat_ABCD range=chr1:1234567-2345678
tgtgcacactacacatgactagtacatgactagac....so on
>mm10_refflat_BCD range=chr1:3234567-4545678...
tgtgcacactacacatgactagtatgtgcacactacacatgactagta
.
.
.
.
.
so on
... (2 Replies)
Hi all,
I have been trying to delete duplicates based on a certain pattern but failed to make it works. There are more than 1 pattern which are duplicated but i just want to remove 1 pattern only and remain the rest. I cannot use awk '!x++' inputfile.txt or sed '/pattern/d' or use uniq and sort... (7 Replies)
Discussion started by: redse171
7 Replies
LEARN ABOUT HPUX
rc.config
rc.config(4) Kernel Interfaces Manual rc.config(4)NAME
rc.config, rc.config.d - files containing system configuration information
SYNOPSIS DESCRIPTION
The system configuration used at startup is contained in files within the directory The file sources all of the files within and and
exports their contents to the environment.
/etc/rc.config
The file is a script that sources all of the scripts, and also sources To read the configuration definitions, only this file need be
sourced. This file is sourced by whenever it is run, such as when the command is run to transition between run states. Each file that
exists in is sourced, without regard to which startup scripts are to be executed.
/etc/rc.config.d
The configuration information is structured as a directory of files, rather than as a single file containing the same information. This
allows developers to create and manage their own configuration files here, without the complications of shared ownership and access of a
common file.
/etc/rc.config.d/* Files
This is where files containing configuration variable assignments are located.
Configuration scripts must be written to be read by the POSIX shell, and not the Bourne shell, or In some cases, these files must also be
read and possibly modified by control scripts or the sam program. See sd(4) and sam(1M). For this reason, each variable definition must
appear on a separate line, with the syntax:
No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the comment character in
column one. This example shows the required syntax for configuration files:
Configuration variables may be declared as array parameters when describing multiple instances of the variable configuration. For example,
a system may contain two network interfaces, each having a unique IP address and subnet mask (see ifconfig(1M)). An example of such a dec-
laration is as follows:
Note that there must be no requirements on the order of the files sourced. This means configuration files must not refer to variables
defined in other configuration files, since there is no guarantee that the variable being referenced is currently defined. There is no
protection against environment variable namespace collision in these configuration files. Programmers must take care to avoid such prob-
lems.
/etc/TIMEZONE
The file contains the definition of the environment variable. This file is required by POSIX. It is sourced by at the same time the files
are sourced.
SEE ALSO rc(1M).
rc.config(4)