Sponsored Content
Special Forums IP Networking Adding an extra route to the ip routing table Post 302141352 by Japie89 on Thursday 18th of October 2007 07:16:43 PM
Old 10-18-2007
Did it! Tnx!
 

10 More Discussions You Might Find Interesting

1. IP Networking

route table command

Im very new to unix.. I want to view the route table whats the command. (1 Reply)
Discussion started by: jhale123
1 Replies

2. UNIX for Dummies Questions & Answers

not following routing table

Hi, I'm trying to connect to a network device, with the connection follwoing the UNIX routing table we set up. Its to go via a specific network Gateway and out throught a specific Lan card (Lan4). However when trying to conenct it keeps going through Lan3 and will not get to its destination.... (3 Replies)
Discussion started by: nhatch
3 Replies

3. UNIX for Dummies Questions & Answers

How do I find route table information

I am trying to install a new AIX server and I am migrating off of an older AIX server. Does anyone have a quick and easy method for getting the static route information from the old server so I can just maybe copy a file over to the new server ? (1 Reply)
Discussion started by: Docboyeee
1 Replies

4. IP Networking

Ip routing table

hi all, how to access ip routing table throgh program, how should i integrate my rip routing table with the ip routing table :) (0 Replies)
Discussion started by: vinodkumar
0 Replies

5. IP Networking

routing table

hi all... i need to know, where is locate the routing table on sun solaris, how i can saved the configuration.... because when i restart the server, lost the configuration.... thank you... Regards... (3 Replies)
Discussion started by: chanfle
3 Replies

6. AIX

automatic new routes in route table.

Hi, IBM Server with AIX 5.2. I have already added a static route for a whole network but everyday some automatic routes to hosts adds up in route table of this server, some of which invalid routes that stops communication of server to that network. If these invalid routes are removed from route... (0 Replies)
Discussion started by: system-admin
0 Replies

7. IP Networking

Routing table

Hi all, I am confusing with routing table, i use linux and iptables. i have 1 internet gateway, and 1 router for VPN. here is my network. eth0=192.168.0.1 eth1=192.168.100.1 192.168.0.0/24 --- eth0(Linux Box)eth1 ---(DSL)---Internet | ... (4 Replies)
Discussion started by: blesets
4 Replies

8. Linux

Routing Table

Hello, how to make entries in routing table perminent (1 Reply)
Discussion started by: teenasuresh
1 Replies

9. Solaris

how do i make a route entry permanent in the routing table on solaris 8?

how do I make sure that the entry in the routing table on Solaris 8 stay permanent after rebooting the server. For example route add 172.20.1.60 -netmask 255.255.255.0 172.20.255.253 Each time the server reboots the entry disappears when using the command netstat -nr (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

10. UNIX for Dummies Questions & Answers

iptables / ip route packet routing with multiple gateways

Hi all. Linux noob here. I was hoping someone could help me with configuring some routing rules on my router, an Asus AC68. The router is connected to two gateways, wan0_gateway and wan1_gateway. I have rules set up in the router gui that will push all traffic from every IP other than my own... (0 Replies)
Discussion started by: Bishi
0 Replies
SIGSET(3)						     Linux Programmer's Manual							 SIGSET(3)

NAME
sigset, sighold, sigrelse, sigignore - System V signal API SYNOPSIS
#include <signal.h> typedef void (*sighandler_t)(int); sighandler_t sigset(int sig, sighandler_t disp); int sighold(int sig); int sigrelse(int sig); int sigignore(int sig); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): sigset(), sighold(), sigrelse(), sigignore(): _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED DESCRIPTION
These functions are provided in glibc as a compatibility interface for programs that make use of the historical System V signal API. This API is obsolete: new applications should use the POSIX signal API (sigaction(2), sigprocmask(2), etc.) The sigset() function modifies the disposition of the signal sig. The disp argument can be the address of a signal handler function, or one of the following constants: SIG_DFL Reset the disposition of sig to the default. SIG_IGN Ignore sig. SIG_HOLD Add sig to the process's signal mask, but leave the disposition of sig unchanged. If disp specifies the address of a signal handler, then sig is added to the process's signal mask during execution of the handler. If disp was specified as a value other than SIG_HOLD, then sig is removed from the process's signal mask. The dispositions for SIGKILL and SIGSTOP cannot be changed. The sighold() function adds sig to the calling process's signal mask. The sigrelse() function removes sig from the calling process's signal mask. The sigignore() function sets the disposition of sig to SIG_IGN. RETURN VALUE
On success, sigset() returns SIG_HOLD if sig was blocked before the call, or the signal's previous disposition if it was not blocked before the call. On error, sigset() returns -1, with errno set to indicate the error. (But see BUGS below.) The sighold(), sigrelse(), and sigignore() functions return 0 on success; on error, these functions return -1 and set errno to indicate the error. ERRORS
For sigset() see the ERRORS under sigaction(2) and sigprocmask(2). For sighold() and sigrelse() see the ERRORS under sigprocmask(2). For sigignore(), see the errors under sigaction(2). CONFORMING TO
SVr4, POSIX.1-2001. These functions are obsolete: do not use them in new programs. POSIX.1-2008 marks sighold(), sigignore(), sigpause(), sigrelse(), and sigset() as obsolete, recommending the use of sigaction(2), sigprocmask(2), pthread_sigmask(3), and sigsuspend(2) instead. NOTES
These functions appeared in glibc version 2.1. The sighandler_t type is a GNU extension; it is used on this page only to make the sigset() prototype more easily readable. The sigset() function provides reliable signal handling semantics (as when calling sigaction(2) with sa_mask equal to 0). On System V, the signal() function provides unreliable semantics (as when calling sigaction(2) with sa_mask equal to SA_RESETHAND | SA_NODEFER). On BSD, signal() provides reliable semantics. POSIX.1-2001 leaves these aspects of signal() unspecified. See signal(2) for further details. In order to wait for a signal, BSD and System V both provided a function named sigpause(3), but this function has a different argument on the two systems. See sigpause(3) for details. BUGS
In versions of glibc before 2.2, sigset() did not unblock sig if disp was specified as a value other than SIG_HOLD. In versions of glibc before 2.5, sigset() does not correctly return the previous disposition of the signal in two cases. First, if disp is specified as SIG_HOLD, then a successful sigset() always returns SIG_HOLD. Instead, it should return the previous disposition of the sig- nal (unless the signal was blocked, in which case SIG_HOLD should be returned). Second, if the signal is currently blocked, then the return value of a successful sigset() should be SIG_HOLD. Instead, the previous disposition of the signal is returned. These problems have been fixed since glibc 2.5. SEE ALSO
kill(2), pause(2), sigaction(2), signal(2), sigprocmask(2), raise(3), sigpause(3), sigvec(3), signal(7) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2010-09-20 SIGSET(3)
All times are GMT -4. The time now is 03:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy