Sponsored Content
Operating Systems Solaris Default route is configured, but seem to not work Post 302534422 by DukeNuke2 on Tuesday 28th of June 2011 01:27:13 AM
Old 06-28-2011
have you restarted the machine?
 

8 More Discussions You Might Find Interesting

1. AIX

Permanent Default Route

Hi, We are running AIX 5.2. Our default gateway used to be IP Address A. Our new default gateway is IP Address B. A netstat revealed that our default route was IP address A. We manually added default route with IP address B and removed the default route with IP address A. However,... (3 Replies)
Discussion started by: DenD
3 Replies

2. AIX

Default route removed - what to do ?

Hi, After accidental default route removal serial connection doesn't work. What should I do to connect to my machine ? thanks Vilius (7 Replies)
Discussion started by: vilius
7 Replies

3. Solaris

solaris 10 u5 what happens if no default route configured

Hi, I am new to solaris 10. What is the procedure the os takes if a default route is not configured? I am using a multihomed server with 4 interfaces. It looked strange to me this morning, because i had not defined a default route it defaulted to making one up, with the ip address of another... (9 Replies)
Discussion started by: borderblaster
9 Replies

4. AIX

Default route question

Hello I have a question regarding default route on AIX servers. (I am using a p5 5.3 TL9 machine). in my output of "lsattr -El inet0" I can see there are two routes like below. route net,-hopcount,0,,0,x.x.207.7 Route True route net,-hopcount,0,,0,x.x.202.129 Route True But... (9 Replies)
Discussion started by: gsabarinath
9 Replies

5. IP Networking

DHCP/pxeboot Situation: how to specify default route?

Greetings, I am using debian squeeze to perform the following operation: 1. pxeboot Alix 2.c board into debian installer When I get to the installer my laptop's dhcp server successfully provides an ip address but does not set up the default route. I am not sure how to provide this. I... (2 Replies)
Discussion started by: mock
2 Replies

6. AIX

Default Route add fails

AIX version 5.3 when I try to add default gateway # route add 0 192.168.100.254 Or # route add default 192.168.100.254 I get the error 0821-275 route: socket: The file access permissions do not allow the specified action. searching on google i came across similar... (5 Replies)
Discussion started by: filosophizer
5 Replies

7. Solaris

Default route in system

Hi All Recently we have faced issue in SUN server after reboot of node 2 default routs has been added to system as below IRE Table: IPv4 **Destination*************Mask***********Gateway**********Device Mxfrg Rtt***Ref Flg**Out**In/Fwd* -------------------- ---------------... (2 Replies)
Discussion started by: aaysa123
2 Replies

8. Red Hat

IP Route add default and make permanet

Hi all, actually i'm facing this problem, we have 2 NICs on our VM.s with REDHAT 7.2 release, we made the following set up as we needed to access them from both IP ip route flush all ip route add 10.130.11.0/24 dev eno2 tab 1 ip route add 10.130.10.0/24 dev eno1 tab 2 ip route add... (0 Replies)
Discussion started by: charli1
0 Replies
RESTART_SYSCALL(2)					     Linux Programmer's Manual						RESTART_SYSCALL(2)

NAME
restart_syscall - restart a system call after interruption by a stop signal SYNOPSIS
int restart_syscall(void); Note: There is no glibc wrapper for this system call; see NOTES. DESCRIPTION
The restart_syscall() system call is used to restart certain system calls after a process that was stopped by a signal (e.g., SIGSTOP or SIGTSTP) is later resumed after receiving a SIGCONT signal. This system call is designed only for internal use by the kernel. restart_syscall() is used for restarting only those system calls that, when restarted, should adjust their time-related parameters--namely poll(2) (since Linux 2.6.24), nanosleep(2) (since Linux 2.6), clock_nanosleep(2) (since Linux 2.6), and futex(2), when employed with the FUTEX_WAIT (since Linux 2.6.22) and FUTEX_WAIT_BITSET (since Linux 2.6.31) operations. restart_syscall() restarts the interrupted system call with a time argument that is suitably adjusted to account for the time that has already elapsed (including the time where the process was stopped by a signal). Without the restart_syscall() mechanism, restarting these system calls would not correctly deduct the already elapsed time when the process continued execution. RETURN VALUE
The return value of restart_syscall() is the return value of whatever system call is being restarted. ERRORS
errno is set as per the errors for whatever system call is being restarted by restart_syscall(). VERSIONS
The restart_syscall() system call is present since Linux 2.6. CONFORMING TO
This system call is Linux-specific. NOTES
There is no glibc wrapper for this system call, because it is intended for use only by the kernel and should never be called by applica- tions. The kernel uses restart_syscall() to ensure that when a system call is restarted after a process has been stopped by a signal and then resumed by SIGCONT, then the time that the process spent in the stopped state is counted against the timeout interval specified in the original system call. In the case of system calls that take a timeout argument and automatically restart after a stop signal plus SIGCONT, but which do not have the restart_syscall(2) mechanism built in, then, after the process resumes execution, the time that the process spent in the stop state is not counted against the timeout value. Notable examples of system calls that suffer this problem are ppoll(2), select(2), and pselect(2). From user space, the operation of restart_syscall() is largely invisible: to the process that made the system call that is restarted, it appears as though that system call executed and returned in the usual fashion. SEE ALSO
sigaction(2), sigreturn(2), signal(7) Linux 2014-12-31 RESTART_SYSCALL(2)
All times are GMT -4. The time now is 01:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy