10 More Discussions You Might Find Interesting
1. Red Hat
Hi all,
I can't port forward from WAN to VPN Client. VPN Client Ubuntu 18 192.168.0.16 Port 6000
VPN Gateway for LAN clients Centos 192.168.0.12
Router 192.168.0.1
I can forward to the VPN Client if VPN is not connected if I forward Port 6000 from 192.168.0.1 directly to 192.168.0.16.... (2 Replies)
Discussion started by: stinkefisch
2 Replies
2. IP Networking
First of all, hello.
I have a problem installing a vpn server and client.
My server is a computer running windows 7, and windows, running a virtual machine running debian.
In the debian system, I've the vpn server installed (SoftEther VPN Server)
The problems come when I try to connect to... (1 Reply)
Discussion started by: Blues23
1 Replies
3. Solaris
I need to install VPN client on Solaris 10 server. I searched but only Cisco client was available which requires a service agreement. Please suggest some free ware for this and the steps to do that too as i am net to Solaris Admin tasks. (1 Reply)
Discussion started by: kukretiabhi13
1 Replies
4. Linux
Hi,
When I googled, I came to know that I can not call the command
"service <service-name> start" from cron, insted I have to specify path to the service-name.
I wanted to know the reason.
Thanks,
Hansini (3 Replies)
Discussion started by: hansini
3 Replies
5. UNIX for Dummies Questions & Answers
Hi Gurus of UNIX, I have a problem when I try to install a software VPN Cisco in Laptop (HP530).
I do the following procedures:
Part 2 - VPN Client Compilation
We will now set up the vpn client. As there is no official Cisco VPN Client for OpenSolaris X86 available, we will use vpnc.... (1 Reply)
Discussion started by: andresguillen
1 Replies
6. Red Hat
Anyone had installed Cisco AnyConnect VPN client on RedHat5.3 EL or CentOS 5.3?
I tried on CentOS 5.3 but always getting host unreachable error. Same for windows xp works fine.
The error log reports:
Sep 1 19:14:03 localhost vpnagent: Function: tableCallbackHandler File: RouteMgr.cpp Line:... (3 Replies)
Discussion started by: zing_foru
3 Replies
7. IP Networking
Hi all,
I am trying to write a script that launch the cisco vpn client from the command line and then connects to a remote host using ssh.
When i connect to the cisco vpn using vpnclient client connect the last lines of output from that client is
Encryption: 168-bit 3-DES
Authentication:... (0 Replies)
Discussion started by: borderblaster
0 Replies
8. IP Networking
Who in the 64 ubuntu adopted cisco vpn client on the wireless network
I downloaded the cisco vpn client for linux but run vpn_install make file when an error in cisco with the help of the document read in half a day, nor do I know this vpn client in the 64 systems in use.
Who can help me, a... (1 Reply)
Discussion started by: Eason
1 Replies
9. Solaris
Hi,
I am working with a company where some times i need to start/stop cron jobs on need basis.
I have one option to kill cron daemon.Is it right?
Please correct me.
Waiting for your reply.
Thanks in advance.. (2 Replies)
Discussion started by: varaprasadu
2 Replies
10. Cybersecurity
I'm looking for an open source VPN client that I can set up on RedHat 7.1.
Any suggestion?
Thanks in advance.
VJ
:) (3 Replies)
Discussion started by: vancouver_joe
3 Replies
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.deny file in order
to use this command.
If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use
this command, or all users will be able to use this command.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is
given.
The -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 19 April 2010 CRONTAB(1)