Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Unable to ping my Ip in sco Unix Post 36433 by TRUEST on Wednesday 28th of May 2003 11:39:24 PM
Old 05-29-2003
I doubt you really have to go thru that pointless task of editing so many files simple because you want change the IP address of a host.

instead of doing it by files, you can first change your IP address the way I prefer way I personally prefer by using the ifconfig command.

Then you put the route command into use to solve the error complaining about "no route to host"

use the route command like:

1. route add default (ipaddress) 1

or

2. route add net (network) (ipaddress) 1

i think in your case, number 2 is what you will or should be using.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to ping host

Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: - 1 QNX host->Eth->1 SCO host the SCO host is configured with it's IP the QNX host is configured with another IP both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies

2. UNIX for Dummies Questions & Answers

unable ping ipaddress

I have Sco openserver 5.0. It had a 125. ip. I changed it to a 192. ip. was unable to ping the 192. I was told to change it in the etc/tcp etc/hosts files which i did. still unable to ping. i am getting a message unable to route to host. I also have an error in my etc/tcp file on line... (1 Reply)
Discussion started by: pdoug76
1 Replies

3. UNIX for Dummies Questions & Answers

unable to ping

DEar all i am receiving this error on start and then unable to ping (dlpid): unable to open network adapter driver (/dev/mdi/e3h0) what to do ? (2 Replies)
Discussion started by: sak900354
2 Replies

4. IP Networking

Unable to ping the gateway IP itself

We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command 64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies

5. Solaris

unable to ping server

hi, I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise? Test that i have done: -My client pc cannot ping the server. -My solaris server cannot ping client -My solaris server can ping it's gateway -Another NT machine 1 (10.179.30.26) in the server... (2 Replies)
Discussion started by: skiturn
2 Replies

6. IP Networking

unable to ping to my server

hi, I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise? Test that i have done: -My client pc cannot ping the server. -My solaris server cannot ping client -My solaris server can ping it's gateway -Another NT machine 1 (10.179.30.26) in the... (8 Replies)
Discussion started by: skiturn
8 Replies

7. SuSE

unable to ping virtualbox machine

I current have Windows 7 running Virtualbox - OpenSUSE. From SUSE I can ping the Windows box 10.10.x.x no problems. But from the windows box I can't ping SUSE. I have tried disabling the firewall and sill no luck. Tried pinging host name and still no luck. The network gives an IP from... (2 Replies)
Discussion started by: woofie
2 Replies

8. Solaris

Unable to ping New server

Hi ALL, I Have installed NEW v240 server through hyper terminal, After installation i unable to ping the server from out side server... i can see no entry in resolve.conf file.. but the server has DNS.. willl that issue.. please guide me ping the server from outside within the same network bk (1 Reply)
Discussion started by: suresh_krish
1 Replies

9. Solaris

Unable to ping Windows

Hello, Am unable to ping the Windows Box, from my Solaris Box. They both are in same LAN, have the same IP Segments. Windows IP :: 10.141.14.120 Solaris IP :: 10.141.14.11 Unable to get why isnt working out.... When using the command 'ping 10.141.14.120', it gives the error as 'ping:... (4 Replies)
Discussion started by: jayanto
4 Replies

10. AIX

Unable to ping localhost

Hi all, I have gone through many posts related to this issue,but my issue wasn't resolved hence creating new thread. I am unable to ping localhost. ping localhost tries to ping localhost which is defined in DNS. My /etc/hosts has entry for localhost as 127.0.0.1 loopback localhost. ... (8 Replies)
Discussion started by: chpsam
8 Replies
CS(1)							  The Canonical Csound Reference						     CS(1)

NAME
cs - Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the specified filename stem. . DESCRIPTION
Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the specified filename stem. SYNTAX
cs [-OPTIONS] <name> [CSOUND OPTIONS ... ] INITIALIZATION
Flags: o - OPTIONS = OPTIONS is a sequence of alphabetic characters that can be used for selecting the Csound executable to be run, as well as the command line flags (see below). There is a default for the option 'r' (selects real-time output), but it can be overridden. o <name> = this is the filename stem for selecting input files; it may contain a path. Files that have .csd, .orc, or .sco extension are searched, and either a CSD or an orc/sco pair that matches <name> the best are selected. MIDI files with a .mid extension are also searched, and if one that matches <name> at least as close as the CSD or orc/sco pair, it is used with the -F flag. NOTE The MIDI file is not used if any -M or -F flag is specified by the user - new in version 4.24.0) Unless there is any option (-n or -o) related to audio output, an output file name with the appropriate extension is automatically generated (based on the name of selected input files and format options). The output file is always written to the current directory. NOTE file name extensions are not case sensitive. o [CSOUND OPTIONS ... ] = any number of additional options for Csound that are simply copied to the final command line to be executed. The command line that is executed is generated from four parts: 1. Csound executable (possibly with options). This is exactly one of the following (the last one has the highest precedence): o a built-in default o the value of the CSOUND environment variable o environment variables with a name in the format of CSOUND_x where x is an uppercase letter selected by characters of the -OPTIONS string. Thus, if the -dcba option is used, and the environment variables CSOUND_B and CSOUND_C are defined, the value of CSOUND_B will take effect. 2. Any number of option lists, added in the following order: o either some built-in defaults, or the value of the CSFLAGS environment variable if it is defined. o environment variables with a name in the format of CSFLAGS_x where x is an uppercase letter selected by characters of the -OPTIONS string. Thus, if the -dcba option is used, and the environment variables CSFLAGS_A and CSFLAGS_C are defined as '-M 1 -o dac' and '-m231 -H0', respectively, the string '-m231 -H0 -M 1 -o dac' will be added. 3. The explicit options of [CSOUND OPTIONS ... ]. 4. Any options and file names generated from <name>. NOTE Quoted options that contain spaces are allowed. EXAMPLES
Assuming the following environment variables: CSOUND = csoundfltk.exe -W CSOUND_D = csound64.exe -J CSOUND_R = csoundfltk.exe -h CSFLAGS = -d -m135 -H1 -s CSFLAGS_D = -f CSFLAGS_R = -m0 -H0 -o dac1 -M "MIDI Yoke NT: 1" -b 200 -B 6000 And a directory that contains: foo.orc piano.csd foo.sco piano.mid im.csd piano2.mid ImproSculpt2_share.csd foobar.csd The following commands will execute as shown: cs foo => csoundfltk.exe -W -d -m135 -H1 -s -o foo.wav foo.orc foo.sco cs foob => csoundfltk.exe -W -d -m135 -H1 -s -o foobar.wav foobar.csd cs -r imp -i adc => csoundfltk.exe -h -d -m135 -H1 -s -m0 -H0 -o dac1 -M "MIDI Yoke NT: 1" -b 200 -B 6000 -i adc ImproSculpt2_share.csd cs -d im => csound64.exe -J -d -m135 -H1 -s -f -o im.sf im.csd cs piano => csoundfltk.exe -W -d -m135 -H1 -s -F piano.mid -o piano.wav piano.csd cs piano2 => csoundfltk.exe -W -d -m135 -H1 -s -F piano2.mid -o piano2.wav piano.csd CREDITS
Author: Istvan Varga Jan 2003 AUTHORS
Barry Vercoe MIT Media Lab Author. Dan Ellis MIT Media Lab, Cambridge Massachussetts Author. COPYRIGHT
5.07 06/23/2009 CS(1)
All times are GMT -4. The time now is 03:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy