10-01-2009
In a hundred words or less, I love this site because:
It's brilliant. I've learnt bucket loads in spades from people on here.
And strangly in the past whenever I "googled" for something and this (or other forums came up) I would avoid them like the plague! Not wanting wishy-washy-waffle, but hard facts! How wrong I was. But this is the best forum sight I have ever seen.
All those wasted years!
A credit to everyone who makes it what it is.
----
Accorging to wc, that's 71 words. Not bad!
8 More Discussions You Might Find Interesting
1. Solaris
Hi guys,
Why is the look and feel of CDE still the same? It hasn't changed at all.
-cadmiumgreen (1 Reply)
Discussion started by: cadmiumgreen
1 Replies
2. What is on Your Mind?
Hi all,
I was just crious to know your thoughts about sudo i.e. does it really enhance security or do you feel that it doesn't provide with much security as Ubuntu folks think :) And also post your personal experiences of using sudo and your first thoughts about it and any suggestions to... (1 Reply)
Discussion started by: tayyabq8
1 Replies
3. IP Networking
Setup a site to site VPN between two cisco routers.
One of the site locations is unable to access ports such as https://example.com:9001
How do I let them go into port 9001?
They can ssh, ftp, telnet and everything else.
Is this a VPN issue or ACL access issue?
I put
permit ip host... (0 Replies)
Discussion started by: photon
0 Replies
4. Solaris
Every once in a while, I take a peek at OpenIndiana, Nexenta and Illumos hoping to see the spirit of OpenSolaris rise and fly.
But I'm not real impressed with the level of activity.
What do you think? Is there still forward progress?
Is there a large reservoir of loyal Solaris users that... (1 Reply)
Discussion started by: KenJackson
1 Replies
5. What is on Your Mind?
I am trying to study this solaris OS. But each time I study, I feel like I didn't learn anything. Any suggestions?
Thanks (4 Replies)
Discussion started by: cjashu
4 Replies
6. IP Networking
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies
7. IP Networking
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
8. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
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 as the number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).
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.
CONFORMING TO
SVr4, 4.3BSD, C89, C99, POSIX.1-2001. POSIX does not specify any error conditions.
NOTES
POSIX.1 defines seconds since the Epoch using a formula that approximates the number of seconds between a specified time and the Epoch.
This formula takes account of the facts that all years that are evenly divisible by 4 are leap years, but years that are evenly divisible
by 100 are not leap years unless they are also evenly divisible by 400, in which case they 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 system clocks are not required to be syn-
chronized to a standard reference. The intention is that the interpretation of seconds since the Epoch values be consistent; see
POSIX.1-2008 Rationale A.4.15 for further rationale.
SEE ALSO
date(1), gettimeofday(2), ctime(3), ftime(3), time(7)
COLOPHON
This page is part of release 3.44 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 2011-09-09 TIME(2)