The solution sort of work / not work, the problem is if there is no match, then xargs does a full listing. That is if it found file/s that matches the search string and hence file exist, it does list the files but if it doesn't find a match it do a full listing instead
See example below:
Code:
$: ls -ltr
total 16
-rw-r----- 1 tester omg 0 Mar 19 09:36 file1
-rw-r----- 1 tester omg 0 Mar 19 09:36 file2
-rw-r----- 1 tester omg 0 Mar 19 09:36 file3
-rw-r----- 1 tester omg 0 Mar 19 09:36 file4
-rw-r----- 1 tester omg 0 Mar 19 09:36 file5
-rw-r----- 1 tester omg 15 Mar 19 09:36 corrupt.txt
$: grep -il "bad" * | xargs ls -l
-rw-r----- 1 tester dba 15 Mar 19 09:36 corrupt.txt
$: grep -il "corrupt" * | xargs ls -l
total 16
-rw-r----- 1 tester omg 15 Mar 19 09:36 corrupt.txt
-rw-r----- 1 tester omg 0 Mar 19 09:36 file1
-rw-r----- 1 tester omg 0 Mar 19 09:36 file2
-rw-r----- 1 tester omg 0 Mar 19 09:36 file3
-rw-r----- 1 tester omg 0 Mar 19 09:36 file4
-rw-r----- 1 tester omg 0 Mar 19 09:36 file5
$: uname -a
SunOS [hostname] 5.11 11.3 sun4v sparc sun4v
$: cat corrupt.txt
BAD FILE FOUND
And just realized I can just actually just do ls -l but it gave me the same behaviour:
Code:
$: ls -l `grep -il "bad" *`
-rw-r----- 1 tester omg 15 Mar 19 09:36 corrupt.txt
$: ls -l `grep -il "corrupt" *`
total 16
-rw-r----- 1 tester omg 15 Mar 19 09:36 corrupt.txt
-rw-r----- 1 tester omg 0 Mar 19 09:36 file1
-rw-r----- 1 tester omg 0 Mar 19 09:36 file2
-rw-r----- 1 tester omg 0 Mar 19 09:36 file3
-rw-r----- 1 tester omg 0 Mar 19 09:36 file4
-rw-r----- 1 tester omg 0 Mar 19 09:36 file5
I guess this is the expected behavior but kinda hoping it'll just do nothing if it doesn't find any or print something maybe instead? Any suggestion?
Hi,
I have a file which is a result of a script running every two minutes. What I wanted to do is to grep a specific date and time (hour and minute) from the file and then count the occurance of 201. I need to get the result of occurance of 201 every 5 minutes. What should I include in my... (8 Replies)
Hi,
I'm trying to accomplish the following and would like some suggestions or possible bash script examples that may work
I have a directory that has a list of log files that's periodically dumped from a script that is crontab that are rotated 4 generations. There will be a time stamp that is... (4 Replies)
I've seen several examples of grep showing the filename the string was found in, but what I really need is grep to show the file details in long format (like ls -l would).
scenario is:
grep mobile_number todays_files
This will show me the string I'm after & which files they turn up in, but... (2 Replies)
Hi,
I have a log file without date/time, and I want that everytime tail|grep find something it displays the date/time and the line. I have tried something like this command but without any luck to display the date/time:
tail -F catalina.out | sed "s/^/`date `/" | egrep ... (6 Replies)
Hi All,
Need a small help. I have a log file which keeps updating for every Minute with multiple number of lines. I just want to grep few properties which has latest Date and Time to it. How do i do it?
I wanted to grep a property by name "Reloading cache with a maximum of" from the... (4 Replies)
how can i grep a range?
i have a text file with the following text:
result.log.00:2012/01/02 12:00:07.422 LOG STARTED HERE
N6Kashya29MemoryShieldScheduler_AO_IMPLE, pid=8662/8658,
config=(alertThreshold=10,alertLevel=0,killThreshold=7200,coreThreshold=0,full=1),
deltaTime=0,... (1 Reply)
Hi guys,
This is probably very easy but I've no idea how to pull this out.
Basically, I need to find errors into a very large logfile. When you grep the ID, the output is like this:
+- Type: 799911 Code: Ret: 22728954 Mand: X Def: Des: UserDes: SeqNo: 2
+- Type: 799911 Code: Ret:... (5 Replies)
I've got a job that finds and removes trace files based upon an access time of more than seven days (I've also tried a modify date).
find TABC* -atime +7 -exec rm +
find TABC* -mtime +7 -exec rm +
Whether I use -atime or -mtime, the process seems to work sporadically. Sometimes it removes... (6 Replies)
I am using grep as follows
grep --include \*.org -ir "sunspot" -C 3 ./astron_aphys/solarsy/sun/helioseism/localhs/fhankel/
This gives me the filename for each matched line. How can I change the command to print the file name only once rather than having the same file name repeated at... (2 Replies)
Hi all,
I have many files included time information, some of them included time range by 30 minutes;
2007-12-27T110000.txt
2007-12-27T120000.txt
2007-12-27T130000.txt
2007-12-27T150000.txt
2007-12-27T153000.txt
2007-12-28T000000.txt
2007-12-28T003000.txt
I only want to echo that... (5 Replies)
Discussion started by: jeo_fb
5 Replies
LEARN ABOUT HPUX
cmdisklock
cmdisklock(1m)cmdisklock(1m)NAME
cmdisklock - manage Serviceguard cluster lock devices.
SYNOPSIS
cmdisklock check path
cmdisklock [-f] reset path
DESCRIPTION
cmdisklock is a tool to check the current state of a Serviceguard cluster lock device. It can also be used to reset the state of the clus-
ter lock device. The need to reset the cluster lock device state could arise if the cluster lock device is replaced or becomes corrupt.
A cluster lock device can be either an HP-UX LVM cluster lock or a cluster lock LUN device. HP-UX LVM cluster locks exist only on a disk
in an LVM volume group. Cluster lock LUNs exist only on disks dedicated to cluster lock. cmdisklock is useful for checking either type of
cluster lock and for re-initializing cluster lock LUN devices after a failure or corruption.
NOTE
To restore an HP-UX LVM cluster lock, use vgcfgrestore. cmdisklock will fail until vgcfgrestore is run, and cmdisklock is unnecessary as
long as vgcfgbackup was done after the cluster lock was initialized. See the Managing Serviceguard manual for details.
The syntax of the path option depends on the type of lock. For HP-UX LVM cluster lock disks, the syntax is VG:PV (for example:
/dev/vglock:/dev/dsk/c0t0d2). For cluster lock LUN disks, the path is the disk device path. For example, /dev/sdd1 (on Linux) or
/dev/dsk/c0t1d2 (on HP-UX).
Options
cmdisklock supports the following options:
check Check the current state of the cluster lock device and report the results.
reset Reset (initialize) the state of the cluster lock device. This operation should only be performed on a cluster lock
LUN device. For HP-UX LVM cluster lock, use vgcfgrestore as documented in the Managing Serviceguard manual. After
performing a reset, a check can be used to verify that the lock is cleared.
EXAMPLES
If the cluster lock LUN device becomes corrupted and the cluster is up, messages like the following will appear in syslog.
Mar 15 12:20:41 usb cmdisklockd[17599]: WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is cor-
rected, a single failure could cause all nodes in the cluster to crash.
Mar 15 12:20:41 usb cmdisklockd[17599]: After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset
/dev/dsk/c0t1d2' to repair
Mar 15 12:20:41 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is inaccessible
Once the above messages appear in syslog on all running nodes, the following command will re-initialize the cluster lock LUN:
ucd:/> cmdisklock reset /dev/dsk/c0t1d2
WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is corrected, a single failure could cause all nodes
in the cluster to crash.
After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset /dev/dsk/c0t1d2' to repair
/dev/dsk/c0t1d2 is inaccessible
Resetting cluster lock device /dev/dsk/c0t1d2
Cluster lock reset completed
/dev/dsk/c0t1d2 is accessible
cleared
After the lock is restored, a message like the following appears in syslog:
Mar 15 12:23:11 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is accessible
WARNINGS
CAUTION
For cluster lock LUN, reset is a potentially destructive operation. While cmdisklock checks for known volume manager and file system use
(overridden by -f), it does not validate that the device to be reset is actually used by any cluster. If -f is used on the wrong device
file, loss of data may result.
CAUTION
Care should be taken when doing a reset when the cluster is active as there is a remote possibility that the cluster will partition right
when this command is run and both nodes could end up thinking they have successfully acquired the lock. To avoid this situation, make sure
cmcld has logged a message in syslog on all running nodes saying the device is inaccessble, before performing a reset. Note that it is
safe to run cmdisklock when the cluster is down.
RETURN VALUE
cmdisklock returns the following values:
0 Successful completion.
1 The disk is inaccessible or is not recognized as a cluster lock.
AUTHOR
cmdisklock was developed by HP.
SEE ALSO cmapplyconf(1m), cmviewcl(1m), vgcfgbackup(1m), vgcfgrestore(1m)
Requires Optional Serviceguard Software cmdisklock(1m)
03-18-2020
