I have written a sample pro*c code and able compile and create a executable file without any error. But I have to run this binary in some other server by FTPing this binary to other server. The directory structure of ORACLE_HOME for both server is different. I used ORACLE_HOME as environmental variable. When I try to run the binary in the target server, it searching the library file in the directory structure of source server where I compiled.
Could you please help..!
Thanks
Akhirul
---------- Post updated at 02:09 AM ---------- Previous update was at 02:08 AM ----------
error:
Moderator's Comments:
Please use code tags next time for your code and data.
this is the seventh problem i'm having with samba.
for some reason, i cannot logon to the domain.
i've created user accounts... and i was able to establish a connection between
the samba server (my PDC) and my workstations by logging in as "root."
however now when i try to logon it gives... (5 Replies)
Hi,
I have two Solaris machines.
1. SunOS X 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1500
2. SunOS Y 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-60
I am trying to buiild a project on both these machines. The Binary output file compiled on machine 2 runs on both the machines. Where... (0 Replies)
Dear All,
I have writen a Pro*c program that does a data base select,insert,update statements and I have scheduled the program to run from crontab,
It is runing fine for the select insert and commit statement till it reaches the update statement , it throws the following error:
SQL On IPB... (2 Replies)
I am trying to compile the pro*C file but gives errors. It says it encountered "std" while it was expecting ; , = ( $ $ORACLE_HOME/bin/proc tradewind/dataaccess/Blob.pcc
Pro*C/C++: Release 10.2.0.3.0 - Production on Fri May 9 11:10:54 2008
Copyright (c) 1982, 2005, Oracle. All rights... (0 Replies)
Hi,
I wrote a small script whose function is to execute the postemsg provided if the threshold breaches.
I want to log this postemsg messages to a log file. But I am not able to do. Can someone throw some light on how to log the output of this. I am pasting a snippet of that code.
... (2 Replies)
I am using grep to match a pattern, but the output is strange.
$ grep -r -o "pattern" *
Gives me:
Binary file foo1 matches
Binary file foo2 matches
Binary file foo3 matches
To find the lines before/after, I then have to use the following on each file:
$ strings foo1 | grep -A1 -B1... (0 Replies)
Hello,
Can I copy a binary file while the file is being written to by another process?
Another process (program) “P1” creates and opens (for writing) binary file “ABC” on local disk. Process P1 continuously write into ABC file every couple of seconds, adding 512-byte blocks of data. ABC file... (1 Reply)
I am struck up with a problem and that is with output redirection.
I used all the ways for the redirection of the output of c binary to a file, still it is failing.
Here are the different ways which I have used:
./a.out | tee -a /root/tmp.txt 2>&1
./a.out | tee -a /root/tmp.txt 1>&1
./a.out |... (2 Replies)
Hello guys,
We had to move from a DC to another, and we are now facing an "issue" with some text files.
Looks like that some of our log files are set as binary:
file TuxConnectorURA.20121012
TuxConnectorURA.20121012: data or International Language text
less TuxConnectorURA.20121012... (2 Replies)
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
Discussion started by: digidax
7 Replies
LEARN ABOUT SUNOS
nis_getservlist
nis_server(3NSL) Networking Services Library Functions nis_server(3NSL)NAME
nis_server, nis_mkdir, nis_rmdir, nis_servstate, nis_stats, nis_getservlist, nis_freeservlist, nis_freetags - miscellaneous NIS+ functions
SYNOPSIS
cc [ flag... ] file... -lnsl [ library... ]
#include <rpcsvc/nis.h>
nis_error nis_mkdir(nis_name dirname, nis_server *machine);
nis_error nis_rmdir(nis_name dirname, nis_server *machine);
nis_error nis_servstate(nis_server *machine, nis_tag *tags, int numtags, nis_tag **result);
nis_error nis_stats(nis_server *machine, nis_tag *tags, int numtags, nis_tag **result);
void nis_freetags(nis_tag *tags, int numtags);
nis_server **nis_getservlist(nis_name dirname);
void nis_freeservlist(nis_server **machines);
DESCRIPTION
These functions provide a variety of services for NIS+ applications.
The nis_mkdir() function is used to create the necessary databases to support NIS+ service for a directory, dirname, on a server, machine.
If this operation is successful, it means that the directory object describing dirname has been updated to reflect that server machine is
serving the named directory. For a description of the nis_server structure, refer to nis_objects(3NSL).
Per-server and per-directory access restrictions can apply to the nis_mkdir() function. See nisopaccess(1).
The nis_rmdir() function is used to delete the directory, dirname, from the specified server machine. The machine parameter cannot be NULL.
The nis_rmdir() function does not remove the directory dirname from the namespace or remove a server from the server list in the directory
object. To remove a directory from the namespace you must call nis_remove() to remove the directory dirname from the namespace and call
thenis_rmdir() for each server in the server list to remove the directory from the server. To remove a replica from the server list, you
need to first call nis_modify() to remove the server from the directory object and then call nis_rmdir() to remove the replica.
Per-server and per-directory access restrictions can apply to nis_rmdir(). See nisopaccess(1).
For a description of the nis_server structure, refer to nis_objects(3NSL).
The nis_servstate() function is used to set and read the various state variables of the NIS+ servers. In particular the internal debugging
state of the servers can be set and queried.
The nis_stats() function is used to retrieve statistics about how the server is operating. Tracking these statistics can help administra-
tors determine when they need to add additional replicas or to break up a domain into two or more subdomains. For more information on read-
ing statistics, see nisstat(1M).
The nis_servstate() and nis_stats() functions use the tag list. The tag list is a variable length array of nis_tag structures whose length
is passed to the function in the numtags parameter. The set of legal tags are defined in the file <rpcsvc/nis_tags.h> which is included in
<rpcsvc/nis.h>. Because these tags can and do vary between implementations of the NIS+ service, it is best to consult this file for the
supported list. Passing unrecognized tags to a server will result in their tag_value member being set to the string unknown. Both of these
functions return their results in malloced tag structure, *result. If there is an error, *result is set to NULL. The tag_value pointers
points to allocated string memory which contains the results. Use nis_freetags() to free the tag structure.
Per-server and per-directory access restrictions can apply to the NIS_SERVSTATE or NIS_STATUS (nis_stats()) operations and their sub-opera-
tions (tags). See nisopaccess(1).
The nis_getservlist() function returns a null terminated list of nis_server structures that represent the list of servers that serve the
domain named dirname. Servers from this list can be used when calling functions that require the name of a NIS+ server. For a description
of the nis_server refer to nis_objects(3NSL). nis_freeservlist() frees the list of servers list of servers returned by nis_getservlist().
Note that this is the only legal way to free that list.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO nisopaccess(1), nisstat(1M), nis_names(3NSL), nis_objects(3NSL), nis_subr(3NSL), attributes(5)NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 16 Dec 2003 nis_server(3NSL)