My program:
__________________________________
#!/bin/ksh
DAY=`date +%y%m%d`
H=`date +%H`
M=`date +%M`
day=`date +%m/%d/%y`
let h=$H-1
echo DAY $DAY
echo H $H
echo M $M
echo day $day
echo h $h
_____________________________________
My result: (3 Replies)
Hi,
I am trying to grep a particular string from the files of 2 different servers without copying and calculate the total count of its occurence on both files.
File structure is same on both servers and for reference as follows:
27-Aug-2010... (4 Replies)
Hello All,
I am learning unix and basically I want to rotate one of my application logs every 1 hour. I need to rotate that file every one hour. I looked in the forums and googled.. but couldn;t get proper information. Requesting you all to kindly guide me.
Our application is running on... (4 Replies)
Hi everyone.
I am still new to UNIX, and am having trouble figuring out how to create a script to scan a log file to look for errors based on a string.
We run AIX 5.3, and would like the ability to report all the instances of WebSphere Broker Execution groups crashing. This script would... (8 Replies)
I have directory /test/logs which has multiple logs:
audit.log
audit.log.1
audit.log.2
audit.log.3
audit.log.4
audit.log.5
audit.log is current log file and audit.log.X are archive log files. I need to search within these log files and count word "error-5" logged within last 6 months... (4 Replies)
Hi friends, I want to convert 24 hour timing to 12 hour please help me...
my data file looks like this..
13-Nov-2011 13:27:36 15.32044 72.68502
13-Nov-2011 12:08:31 15.31291 72.69807
16-Nov-2011 01:16:54 15.30844 72.74028
15-Nov-2011 20:09:25 15.35096 ... (13 Replies)
Hi there,
I have a script that I've used to find errors in my Minecraft Server logs. But I'd like to refine that script to be more useful.
Here is the script:
grep -n "SEVERE" /minecraft/server.log | awk -F":" '{print $1-2 "," $1+10 "p"}' | xargs -t -i sed -n {} /minecraft/server.log >>... (15 Replies)
Hi Guys,
I want to write a script which can grep the logs (server.log) from a file for Error String and output to a other file.
Problems:
How to know about the errors only between the current restart and not in previous as server.log has earlier restarts also?
thanks for the help! Much... (5 Replies)
Discussion started by: ankur328
5 Replies
LEARN ABOUT ULTRIX
lb_lookup_object
lb_lookup_object(3ncs)lb_lookup_object(3ncs)Name
lb_lookup_object - look up information about an object in the Global Location Broker database
Syntax
#include <idl/c/lb.h>
void lb_$lookup_object(object, lookup_handle, max_num_results, num_results, results, status)
uuid_$t *object;
lb_$lookup_handle_t *lookup_handle;
unsigned long max_num_results;
unsigned long * num_results;
lb_$entry_t results[ ];
status_$t *status;
Arguments
object The UUID of the object being looked up.
lookup_handle A location in the database. On input, the lookup_handle indicates the location in the database where the search
begins. An input value of lb_$default_lookup_handle specifies that the search will start at the beginning of the data-
base. On return, the lookup_handle indicates the next unsearched part of the database (that is, the point at which the
next search should begin). A return value of lb_$default_lookup_handle indicates that the search reached the end of
the database; any other return value indicates that the search found at most max_num_results matching entries before it
reached the end of the database.
max_num_results The maximum number of entries that can be returned by a single routine. This should be the number of elements in the
results array.
num_results The number of entries that were returned in the results array.
results An array that contains the matching GLB database entries, up to the number specified by the max_num_results parameter.
If the array contains any entries for servers on the local network, those entries appear first.
status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it
was successful.
Description
The routine returns GLB database entries whose object field matches the specified object UUID.
The routine cannot return more than max_num_results matching entries at a time. The lookup_handle parameter enables you to find all match-
ing entries by doing sequential lookups.
If you use a sequence of lookup routines to find entries in the database, it is possible that the returned results will skip or duplicate
entries. This is because the Location Broker does not prevent modification of the database between lookups, and such modification can
change the locations of entries relative to a lookup_handle value.
It is also possible that the results of a single lookup routine will skip or duplicate entries. This can occur if the size of the results
exceeds the size of an RPC packet (64K bytes).
Examples
The following statement, looks up GLB database entries for the object identified by :
lb_$lookup_object(&bank_id, &lookup_handle,
MAX_LOCS, &n_locs, bank_loc, &status);
Diagnostics
This section lists status codes for errors returned by this routine in
lb_$database_invalid
The format of the Location Broker database is out of date. The database may have been created by an old version of the
Location Broker; in this case, delete the out-of-date database and reregister any entries that it contained. The LLB
or GLB that was accessed may be running out-of-date software; in this case, update all Location Brokers to the current
software version.
lb_$database_busy The Location Broker database is currently in use in an incompatible manner.
lb_$not_registered The Location Broker does not have any entries that match the criteria specified in the lookup or unregister routine.
The requested object, type, interface, or combination thereof is not registered in the specified database. If you are
using an or routine specifying an LLB, check that you have specified the correct LLB.
lb_$cant_access The Location Broker cannot access the database. Among the possible reasons:
1. The database does not exist.
2. The database exists, but the Location Broker cannot access it.
lb_$server_unavailable
The Location Broker Client Agent cannot reach the requested GLB or LLB. A communications failure occurred or the bro-
ker was not running.
FilesSee Alsointro(3ncs), lb_lookup_interface(3ncs), lb_lookup_object_local(3ncs), lb_lookup_range(3ncs), lb_lookup_type(3ncs)lb_lookup_object(3ncs)