I am having problems with a sparc5 solaris 7 box, when i try to edit cron, (crontab -e as root), it says
$ crontab -e
0
and then nothing, if i enter anything it errors out but does accept q for quit. But doesn't bring up my editor of the cron file. How can I troubleshoot this?
... (3 Replies)
Hi,
I have put the following entry in crontab and it is NOT working
1 * * * * && /mybin/myjob.sh
As today is Sep 26th, Iam using NF-4 to test.
Thanks (2 Replies)
Dear all
We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250
i have scheduled cronjob but its not working
Crontab details
15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247
15 15 * * * mkdir -p rajesh /d4/appltest
Crontab log details
> CMD: mkdir... (4 Replies)
Hi,
I had setup crontab to execute my script every day midnight 00:00
Below are the current settings.
crontab -l
0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1
Should it not work?
I need help fix this? (8 Replies)
I can run manually script of ntopdump.sh but crontab can't run this script very five minutes.
# crontab -l
*/3 * * * * root sh /root/ping.sh
*/5 * * * * root sh /root/ntopdump.sh
#
# pwd
/root
# ls -l
total 88
-rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg
drwxrwxr-x 2 root... (14 Replies)
Shell = ksh
Hi all,
I scheduled an automated job on my application server like below,
30 13 * * 1-5 $HOME/my_script.sh
However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Hi,
When I set the crontab to run every minute, every hour, it works fine.
* * * * * env > /tmp/env.output
However I want to run it every day at 8:00 AM and it does not run.
* 8 * * * env > /tmp/env.output
I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Hi,
I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work:
My cron is running:
UID PID PPID C STIME TTY TIME CMD
root 3755 1 0 Nov27 ? 00:00:00 crond
This... (4 Replies)
Hi All,
I have a script with deatils as :
$ ls -ld catch_logs.sh
-rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh
User crontab looks likes:
$ crontab -l
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
* * * * * /opt/scripts/catch_logs.sh
Now if I run this script... (7 Replies)
Dear Friends,
I have Red Hat Linux Enterprise version 6.3. running SAP and oracle.
I have created one crontab for user orasid to execute one job periodically.
But it is not executing. I have checked crontab service is running.
Please help in the matter.
Regards,
Bhagawati Pandey (5 Replies)
Discussion started by: BPANDEY
5 Replies
LEARN ABOUT DEBIAN
ipsec_klipsdebug
IPSEC_KLIPSDEBUG(5) [FIXME: manual] IPSEC_KLIPSDEBUG(5)NAME
ipsec_klipsdebug - list KLIPS (kernel IPSEC support) debug features and level
SYNOPSIS
ipsec klipsdebug
cat/proc/net/ipsec_klipsdebug
DESCRIPTION
/proc/net/ipsec_klipsdebug lists flags that control various parts of the debugging output of KLIPS and MAST, two of the IPsec stacks
supported by Openswan. At this point it is a read-only file.
A table entry consists of:
+
a KLIPS debug variable
+
a '=' separator for visual and automated parsing between the variable name and its current value
+
hexadecimal bitmap of variable's flags.
The variable names roughly describe the scope of the debugging variable. Currently, no flags are documented or individually accessible yet
except tunnel-xmit.
The variable names are:
tunnel
tunnelling code
netlink
userspace communication code (obsolete)
xform
transform selection and manipulation code
eroute
eroute table manipulation code
spi
SA table manipulation code
radij
radij tree manipulation code
esp
encryptions transforms code
ah
authentication transforms code
rcv
receive code
ipcomp
ip compression transforms code
verbose
give even more information, beware this will probably trample the 4k kernel printk buffer giving inaccurate output
All KLIPS debug output appears as kernel.info messages to syslogd(8). Most systems are set up to log these messages to /var/log/messages.
EXAMPLES
debug_tunnel=00000010.
debug_netlink=00000000.
debug_xform=00000000.
debug_eroute=00000000.
debug_spi=00000000.
debug_radij=00000000.
debug_esp=00000000.
debug_ah=00000000.
debug_rcv=00000000.
debug_pfkey=ffffffff.
means that one tunnel flag has been set (tunnel-xmit), full pfkey sockets debugging has been set and everything else is not set.
FILES
/proc/net/ipsec_klipsdebug, /usr/local/bin/ipsec
SEE ALSO ipsec(8), ipsec_manual(8), ipsec_tncfg(8), ipsec_eroute(8), ipsec_spi(8), ipsec_spigrp(8), ipsec_klipsdebug(5), ipsec_version(5),
ipsec_pf_key(5)HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.
[FIXME: source] 10/06/2010 IPSEC_KLIPSDEBUG(5)