hey.....
i do have text where the contents are like as follows,
FILE_TYPE_NUM_01=FILE_TYPE=01|FILE_DESC=Periodic|FILE_SCHDL_TYPE=Daily|FILE_SCHDL=|FILE_SCHDL_TIME=9:00am|RESULTS=B
FILE_TYPE_NUM_02=FILE_TYPE=02|FILE_DESC=NCTO|FILE_SCHDL_TYPE=Daily|FILE_SCHDL=|FILE_SCHDL_TIME=9:00am|RESULTS=M... (2 Replies)
Hi,
Can anyone help me with the text editing I need here. I have a file that contains the following lines for example: (line numbers are for illustration only)
1 Hello world fantasy.
2 Hello worldfuntastic.
3 Hello world wonderful.
I would like to get all those lines of text that... (5 Replies)
Hi
This time I'm trying to grep for an exact match
e.g
cat.dog.horse.cow.bird.pig
horse.dog.pig
pig.cat.horse.dog
horse
dog
dog
pig.dog
pig.dog.bird
how do I grep for dog only so that a wc -l would result 2 in above case.
Thanks in advance
---------- Post updated at 06:33 AM... (4 Replies)
I have a file that contains the 2 following lines (from /proc/mounts)
/dev/sdc1 /mnt/backup2 xfs rw,relatime,attr2,noquota 0 0
/dev/sdb1 /mnt/backup xfs rw,relatime,attr2,noquota 0 0
I need to match the string in the second column exactly so that only one result is returned, e.g.
> grep... (2 Replies)
QUESTION1:
How do you grep only an exact string. I am using Solaris10 and do not have any GNU products installed.
Contents of car.txt
CAR1_KEY0
CAR1_KEY1
CAR2_KEY0
CAR2_KEY1
CAR1_KEY10
CURRENT COMMAND LINE: WHERE VARIABLE CAR_NUMBER=1 AND KEY_NUMBER=1
grep... (1 Reply)
This was mistaken as homework in a different forum, but is not. These are questions that are close to what I am trying to do at work.
QUESTION1:
How do you grep only an exact string. I am using Solaris10 and do not have any GNU products installed.
Contents of car.txt
CAR1_KEY0
CAR1_KEY1... (1 Reply)
This post was previously mistaken for homework, but is actually a small piece of what I working on at work. Please answer if you can.
QUESTION1
How do you grep only an exact string. I am using Solaris10 and do not have any GNU products installed.
Contents of car.txt
CAR1_KEY0
CAR1_KEY1... (2 Replies)
Hello!
I have 2 files named tacs.tmp and tacDB.txt
tacs.tmp looks like this
0
10235647
102700
106800
107200
1105700
tacDB.txt looks like this
100100,Mitsubishi,G410,Handheld,,0,0,0
100200,Siemens,A53,Handheld,,0,0,0
100300,Sony Ericsson,TBD (AAB-1880030-BV),Handheld,,0,0,0... (2 Replies)
Dear All,
Here is my input
TAACGCACTTGCGGCCCCGGGATAAAAAAAAAAAAAAAAAAAAATGGATT
NAGAGGGACGGCCGGGGGCATAAAAAAAAAAAAAAAAAAAAAGGGATTTC
NGGGTTTTAAGCAGGAGGTGTCAAAAAAAAAAAAAAAAAAAAAGGGATTT
NTGGAACCTGGCGCTAGACCAAAAAAAAAAAAAAAAAAAATGGATTTTTG
ATACTTACCTGGCAGGGGAGATACCATGATCAATAAAAAAAAAAAAAAAA... (3 Replies)
Discussion started by: jacobs.smith
3 Replies
LEARN ABOUT SUSE
locks
locks(5) System Tools locks(5)NAME
locks - libzypp locking file
DESCRIPTION
The file /etc/zypp/locks is read by libzypp at startup if zypp.conf allows it. The entries are used for initial locking of packages. Lock-
ing a package means not allowing to install or uninstall it. Valid entries are
attribute: value
Where attributes and their values are described below.
Locks are separated by empty lines.
ATTRIBUTES
All attributes are lower-case.
repo specifies repository restriction. Only alias is accepted.
By default all repositories match.
type resolvable type restriction
The values can be package, patch, pattern, product and srcpackage.
By default all types match.
case_sensitive
if strings are matched case sensitive. The values are true, false, on, off.
The default is case insensitive.
install_status
status of object. Possible states are installed, not-installed and all. If more install statuses are specified then the last one is
used.
The values are installed for all packages which are installed, non-installed for packages which can be installed or reinstalled and
all for both.
The default is all.
match_type
type of string matching in values. Does not affect type and repo which must be specified exactly.
The values are exact, substring, regex for regular expressions, glob for matching as on the command line, and word.
The default is substring.
query_string
String to be matched in multiple attributes. Should be restricted by another attribute with empty value ( it is recommended, because
without restriction expect some performance problems ).
version
Restrict the lock only to some versions. It contains two parts: an optional operator and the version.
The operator is ==,!=,<,>,<=,>=. If operator is not specified then == is used.
The version has the format [epoch:]version[-release].
Example: version: < 0:0.11.4-2
solvable_name
name of object (e.g. zypper)
solvable_summary
summary of object
solvable_arch
architecture of object (e.g. x86_64, i586)
solvable_description
description of object
solvable_eula
license text of objects which request accepting license by user
solvable_license
license of package (only for package) (e.g. GPL2)
solvable_keywords
keywords which specify package (only for package)
solvable_authors
authors of package (only for package)
solvable_group
package group (only for package) (e.g. Development/Tools/Version Control )
update_reference_type
reference for update (e.g. bugzilla,cve) (only for patches)
EXAMPLES
Exact Package
This is the way YaST UI does it. Lock k3b (e.g. you don't want to update it).
-----locks-----
type: package
solvable_name: k3b
match_type: exact
case_sensitive: on
Package Wildcard
This is the way "zypper addlock cross-*-gcc-icecream-backend" does it.
-----locks-----
type: package
solvable_name: cross-*-gcc-icecream-backend
match_type: glob
case_sensitive: on
Versioned Lock
Do not install new GCC. This format is used when converting from the openSUSE-10.3 lock format.
-----locks-----
solvable_name: gcc
match_type: glob
version: > 4.2
Anything named KDE
Locks everything which contains kde in the name.
-----locks-----
solvable_name: kde
Anything mentioning KDE
Locks everything which contains kde in the name, summary, or description.
-----locks-----
query_string: kde
solvable_name:
solvable_summary:
solvable_description:
HOMEPAGE
This manual page only covers the most important attributes. The complete list is available at http://en.opensuse.org/Libzypp/Locksfile
AUTHORS
Josef Reidinger <jreidinger@suse.cz>
Manual page contributions by Martin Vidner <mvidner@suse.cz>.
SEE ALSO zypper(8)libzypp 4.25.0 locks(5)