hey,
I want to concat whole bunch of strings together but somehow they don't turn out the way I want them to
a="HELLO "
b="WORLD "
c=$a$b
I was expecting c to be "HELLO WORLD " but it... (1 Reply)
hi
I have a file, I need to concatenate depening on the no of columns i need to concatenate.
for example i need to concatenate field1,filed34,field2( no of columns is not always 3, it can be any number of fields)
concat.ksh field1 field34 field2
how to achieve this, is there any argv ,argc... (10 Replies)
Hi All
this may be somewhere in internet , but couldnt find the it.
i have file as
abc01
2010-07-01 12:45:24
2010-07-01 12:54:35
abc02
2010-07-01 12:59:24
2010-07-01 01:05:13
abc03
.
.
.
the output using awk should look like this
abc01|2010-07-01 12:45:24|2010-07-01 12:54:35... (3 Replies)
Hello Unix gurus,
how to concat 3 files content side by side .
i have 3 files
more report1.txt
select *from tab1 A JOIN tab1 B ON
more report2.txt
A.PK1=B.PK1 where
more report3.txt
A.AAA <> B.AAA or
A.BBB <> B.BBB or
A.CCC<> B.CCCC or
..
..
..
A.ZZZ <> B.ZZZ;
if i concatinate... (3 Replies)
Hi Folks
The below is code is giving me value 30.
cal | sed '/^$/d' | tail -1 | awk '{printf $NF-1}'
Actually the text is like below.
echo "you should reply on 30-Jan-2013 evening EST.
Here how should i con-cat above logic in that text? (1 Reply)
Hi,
I need help to combine the first 7 character of firstname if it is longer than 7and combine with the first character of lastname.
ex: username lastname => usernaml
user lastname => userl
Thanks in advance. (10 Replies)
All,
I have 2 files A and B with some data. Now i want to concat data from both the files in to 3rd file.Please help me with a single command line.
A--123456789
B--jlsjdfkajsjas
output file C should be 123456789,jlsjdfkajsjas (2 Replies)
Discussion started by: kiranparsha
2 Replies
LEARN ABOUT OSX
ctwatch
ctwatch(1) User Commands ctwatch(1)NAME
ctwatch - watch events in a contract or group of contracts
SYNOPSIS
/usr/bin/ctwatch [-f] [-r] [-v] contract-type... | contract-id...
DESCRIPTION
The ctwatch utility allows a user to observe the events occurring within a set of contracts or contract types. By default, ctwatch watches
all contracts.
OPTIONS
The following options are supported:
-f Report events starting at the front of the event queue. Normally, ctwatch reports only events which occur after it has been
invoked. With the -f option, any events that still exist in the contracts' event queues when ctwatch is invoked (for example,
unacknowledged critical events) are also reported.
-r Reliably watches all messages. Normally, the system may drop informative events and acknowledged critical events at any time, so
ctwatch isn't guaranteed to see them all. This option may only be used if the ctwatch is invoked with the {PRIV_CONTRACT_EVENT}
privilege asserted in its effective set.
-v Request verbose event descriptions.
OPERANDS
The following operands are supported:
contract-type Valid contract types are:
process Process contracts.
contract-id A valid contract id.
OUTPUT
The following list defines the column headings and the meanings of a ctwatch report:
CTID The contract ID generating the event.
EVID The event ID.
CRIT Whether the event is informative, critical, or initiates an exit negotiation. Values are info, crit, or neg, respectively.
ACK The event has been acknowledged. Values are yes or "no".
CTTYPE The contract type.
SUMMARY A type-specific summary of the event.
EXAMPLES
Example 1: Watching a process contract
example% ctwatch -r 1
CTID EVID CRIT ACK CTTYPE SUMMARY
1 2 crit no process pid 100569 was created
1 3 info no process pid 100569 encountered hardware error
1 4 info no process pid 100568 exited
1 5 info no process pid 100569 exited
1 6 crit no process contract empty
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
2 Invalid arguments.
FILES
/system/contract/*
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
Human Readable Output is Unstable. Invocation is Evolving.
SEE ALSO ctrun(1), ctstat(1), contract(4), process(4), attributes(5), privileges(5)NOTES
Ordering of events is only guaranteed within a single contract, or within a single type when a type is specified.
ctwatch can only observe those events which are generated by contracts owned or authored by processes with the same effective user ID as
ctwatch, unless the {PRIV_CONTRACT_OBSERVER} privilege is asserted in its effective set.
SunOS 5.10 14 Jul 2004 ctwatch(1)