unixware 2.0


 
Thread Tools Search this Thread
Operating Systems SCO unixware 2.0
# 1  
Old 11-06-2008
unixware 2.0

High,
I have a simulator application running on unixware 2.1, there are no original installation CDs for the application. is it possible to copy directories and configuration files, related to the installed application, from unixware 2.1 to other system running Unixware 7.1.1 (replacing Unixware 7.1.1 directories).
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. SCO

UnixWare 2.x needed

Anyone here using Unixware 2.x? I want to try some binary testing on this system regarding DG/UX binaries. (4 Replies)
Discussion started by: dgux
4 Replies

2. SCO

Unixware Crash ...

Hi, I need help, one of our servers is down, and all data in that Server are critical: The Scenario: ------------- I have a computer with the next architecture: architecture=IA32 bus_types=PCI2.10,ISA,PnP1.0 hostname=xxx.xxx.xxx (the real name is hidden) hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
2 Replies

3. News, Links, Events and Announcements

Are the UnixWare 7.1.1 sources available?

So, I was browsing groklaw.net, and I was surprised to read that Pamela Jones was reading the copyright notices in the UnixWare 7.1.1 source code files... Groklaw - Santa Cruz Listed Novell as Owning the Copyrights in 1999 How can that be? Are the UnixWare 7.1.1 sources available to the... (1 Reply)
Discussion started by: pepinox
1 Replies

4. SCO

Installing UNIXWARE 7.1.1

I want to install unixware 7.1.1 on a server which does not have a on board floppy drive. I have got a USB floppy drive. Can anybody please help me...how could I provide HBA disk using this USB floppy drive???? (0 Replies)
Discussion started by: siddhartha7m
0 Replies

5. SCO

Unixware 7.11 cannot telnet

Hi all, I recently re-installed a Unixware 7.1.1 system for a customer. It installed correctly, I can ping the server but I cannot telnet to it. I did check and telnetd is running. Am i missing something in the config? thanks for any help (0 Replies)
Discussion started by: RDP
0 Replies

6. SCO

Problem in Unixware 7

Hi, I need help for SCO UNIXWARE 7.1.0. During booting it is detecting the network card (Intel PRO 100B /100+) but it is giving error : "UX:S69inet:error". Hence network is not getting up. I have tried with another network card (D-Link DFE 538TX) but unable to get the proper driver for the... (1 Reply)
Discussion started by: hcl.rajat
1 Replies

7. SCO

Unixware problem

Dear All, I have a HP Netserver LH3 server which has unixware 7 os with oracle. Suddenly it shows a error message that " Raw Stack Dump beigns at 0xFFFDABIC... Generating Selective dump Storing system memory image for crash analysis.... #scanning memory....dumping to disk (Press any key to... (0 Replies)
Discussion started by: mr.chiranjib
0 Replies

8. UNIX for Dummies Questions & Answers

please help me about unixware 7.1.3

msg: vfs_mountroot:cannot mount root %%%%%% system don't start (0 Replies)
Discussion started by: hushboy
0 Replies

9. SCO

Performance issue from Unixware 2.1 to Unixware 7

Hello, I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0. My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls. What i hyave noticed is that after a... (0 Replies)
Discussion started by: Amith
0 Replies

10. IP Networking

Change ip on UnixWare 2.1.2

I changed the IP whit Ifconfig and I used ping to test the conetions the conection is rigth on my LAN (NetA) But, I have two networks for example: NetA route to NetB and vicevers On NetB ping to any machine on NetA, it is respons successfully. but I ping to UNIX server no respons. I... (1 Reply)
Discussion started by: lmena
1 Replies
Login or Register to Ask a Question
SNMP_CONFIG(5)							     Net-SNMP							    SNMP_CONFIG(5)

NAME
snmp_config - handling of Net-SNMP configuration files DESCRIPTION
The Net-SNMP package uses various configuration files to configure its applications. This manual page merely describes the overall nature of them, so that the other manual pages don't have to. DIRECTORIES SEARCHED
First off, there are numerous places that configuration files can be found and read from. By default, the applications look for configura- tion files in the following 4 directories, in order: /etc/snmp, /usr/share/snmp, /usr/lib/snmp, and $HOME/.snmp. In each of these directo- ries, it looks for files with the extension of both conf and local.conf (reading the second ones last). In this manner, there are 8 default places a configuration file can exist for any given configuration file type. Additionally, the above default search path can be overridden by setting the environment variable SNMPCONFPATH to a colon-separated list of directories to search for. The path for the persistent data should be included when running applications that use persistent storage, such as snmpd. Applications will read persistent configuration files in the following order of preference: file in SNMP_PERSISTENT_FILE environment variable directories in SNMPCONFPATH environment variable directory defined by persistentDir snmp.conf variable directory in SNMP_PERSISTENT_DIR environment variable default /var/db/net-snmp directory Finally, applications will write persistent configuration files in the following order of preference: file in SNMP_PERSISTENT_FILE environment variable directory defined by persistentDir snmp.conf variable directory in SNMP_PERSISTENT_DIR environment variable default /var/db/net-snmp directory Note: When using SNMP_PERSISTENT_FILE, the filename should match the application name. For example, /var/net-snmp/snmpd.conf. CONFIGURATION FILE TYPES
Each application may use multiple configuration files, which will configure various different aspects of the application. For instance, the SNMP agent (snmpd) knows how to understand configuration directives in both the snmpd.conf and the snmp.conf files. In fact, most applications understand how to read the contents of the snmp.conf files. Note, however, that configuration directives understood in one file may not be understood in another file. For further information, read the associated manual page with each configuration file type. Also, most of the applications support a -H switch on the command line that will list the configuration files it will look for and the directives in each one that it understands. The snmp.conf configuration file is intended to be a application suite wide configuration file that supports directives that are useful for controlling the fundamental nature of all of the SNMP applications, such as how they all manipulate and parse the textual SNMP MIB files. SWITCHING CONFIGURATION TYPES IN MID-FILE It's possible to switch in mid-file the configuration type that the parser is supposed to be reading. Since that sentence doesn't make much sense, lets give you an example: say that you wanted to turn on packet dumping output for the agent by default, but you didn't want to do that for the rest of the applications (ie, snmpget, snmpwalk, ...). Normally to enable packet dumping in the configuration file you'd need to put a line like: dumpPacket true into the snmp.conf file. But, this would turn it on for all of the applications. So, instead, you can put the same line in the snmpd.conf file so that it only applies to the snmpd daemon. However, you need to tell the parser to expect this line. You do this by putting a spe- cial type specification token inside a [] set. In other words, inside your snmpd.conf file you could put the above snmp.conf directive by adding a line like so: [snmp] dumpPacket true This tells the parser to parse the above line as if it were inside a snmp.conf file instead of an snmpd.conf file. If you want to parse a bunch of lines rather than just one then you can make the context switch apply to the remainder of the file or until the next context switch directive by putting the special token on a line by itself: # make this file handle snmp.conf tokens: [snmp] dumpPacket true logTimestamp true # return to our original snmpd.conf tokens: [snmpd] rocommunity mypublic COMMENTS
Any lines beginning with the character '#' in the configuration files are treated as a comment and are not parsed. INCLUDING OTHER CONFIGURATION FILES
It is possible to include other configuration files for processing during normal configuration file processing.: # include site specific config include site.conf This will search every directory in the configuration path for files named site.conf, and will process those files before returning to the processing of the original file. Note that if '.conf' is omitted, it will be appended. That is, all configuration files must end in '.conf'. API INTERFACE
Information about writing C code that makes use of this system in either the agent's MIB modules or in applications can be found in the netsnmp_config_api(3) manual page. SEE ALSO
snmpconf(1), netsnmp_config_api(3), snmp.conf(5), snmpd.conf(5) V5.6.2.1 08 Mar 2010 SNMP_CONFIG(5)