Network lost after reboot


 
Thread Tools Search this Thread
Operating Systems SCO Network lost after reboot
# 8  
Old 07-23-2007
Sorry for overlooking the first thing that came to mind, but I assume you've ensured that you have a default route added somewhere in a startup script in /etc/rc2.d ??

For instance:

route add default <gateway ip address>


Just making sure. Sometimes it's the obvious stuff that gets overlooked.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Changing "rx_queue_number" in "ixgbe.conf". Reboot or Network Restart?

Hi all, First post here. Working on Solaris 10, on a Sun t4-4, need to change RX queue depth(ethernet, not HBA) and was wondering if i could get by with just restarting the network or if i should just bounce the whole shebang. Apologies if i missed a similar thread. if there is one, please... (2 Replies)
Discussion started by: caspnx
2 Replies

2. IP Networking

Finding lost machine on network trouble

Couldn't find my PC on network. Root of evil the was in bad patch-cable. (0 Replies)
Discussion started by: useretail
0 Replies

3. UNIX for Dummies Questions & Answers

Will authconfig make permanent change or lost after reboot?

Hi, I made following configuration to create user directory: # authconfig --enablemkhomedir --update But the directory is created as permission 755, I'd like to modify the script to change directory access permission to 700, where is the script which copies /etc/skel to /home... (0 Replies)
Discussion started by: hce
0 Replies

4. SuSE

reboot and boot from network

Hello, Does any one know any command which reboot the system and select as boot device the network. I give bootnet to many servers at once and i want to avoid opening ILOM and select as boot device the network. Can i do it by just executing a command? Thanks in advance (2 Replies)
Discussion started by: @dagio
2 Replies

5. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

6. Solaris

[help]network error after reboot server v890 sparc

hi expert, i had reinstall the sun v890 server solaris 8 and also do mirroring, i had configure the network for the server (hostname.eri0,hosts,netmasks,nodename,etc) after i reboot get and error messages below : Setting default IPv4 interface for multicast: add net 224.0/4: gateway... (5 Replies)
Discussion started by: bucci
5 Replies

7. Solaris

Network Connectivity lost after reboot

I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a. Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies
Login or Register to Ask a Question
TIME(2) 						     Linux Programmer's Manual							   TIME(2)

NAME
time - get time in seconds SYNOPSIS
#include <time.h> time_t time(time_t *t); DESCRIPTION
time returns the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds. If t is non-NULL, the return value is also stored in the memory pointed to by t. RETURN VALUE
On success, the value of time in seconds since the Epoch is returned. On error, ((time_t)-1) is returned, and errno is set appropriately. ERRORS
EFAULT t points outside your accessible address space. NOTES
POSIX.1 defines seconds since the Epoch as a value to be interpreted as the number of seconds between a specified time and the Epoch, according to a formula for conversion from UTC equivalent to conversion on the naive basis that leap seconds are ignored and all years divisible by 4 are leap years. This value is not the same as the actual number of seconds between the time and the Epoch, because of leap seconds and because clocks are not required to be synchronised to a standard reference. The intention is that the interpretation of sec- onds since the Epoch values be consistent; see POSIX.1 Annex B 2.2.2 for further rationale. CONFORMING TO
SVr4, SVID, POSIX, X/OPEN, BSD 4.3 Under BSD 4.3, this call is obsoleted by gettimeofday(2). POSIX does not specify any error conditions. SEE ALSO
ctime(3), date(1), ftime(3), gettimeofday(2) Linux 2.0.30 1997-09-09 TIME(2)