07-26-2005
Thanks for the suggestion, but no that can't be the case.
This occurs when logged in as root, which is always the case for us on these systems, i.e. we never log in as anything else.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
i am trying to automate a process and have to create a unix script like wise. I have a scenario in which i need to automate a file movement. Below are the steps i need to automate.
1. Check whether a file (Not Fixed name-Pattern search of file say 'E*.dat') is present in a... (2 Replies)
Discussion started by: imu
2 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I have problem in executing a shell script. When the shell script is executed at the shell prompt the script works successfully but when the same script is run as a cron job it fails to execute the files called within the shell script.
I have scheduled the job in my crontab file as
... (6 Replies)
Discussion started by: forumthreads
6 Replies
3. UNIX for Dummies Questions & Answers
I have a lot of jobs scheduled using at command.
at -l gives only the job names and time ... how do i know which script is associated with which jobid.
Thanks. (1 Reply)
Discussion started by: blackeyed
1 Replies
4. Shell Programming and Scripting
Hi
I need to run a script every five minutes and it should run between 07-15 hours all days.
How i can achieve this...
i tried like this
*/5 07-15 * * * /scripts/CreateFtpData.sh
It throws an error... (1 Reply)
Discussion started by: aemunathan
1 Replies
5. Programming
Hi,
Though this is a unix forum mainly, am posting this oracle query here hoping to get a resolution.
I have set up two scheduled jobs in oracle 11g for executiong a procedure in specific time intervals. One as Hourly and other as minutely.
But the scheduled jobs are not running as per... (2 Replies)
Discussion started by: suresh_kb211
2 Replies
6. UNIX for Dummies Questions & Answers
I have scheduled couple of shell scripts to run using 'at' command.
The o/p of at -l is:
$ at -l
1320904800.a Thu Nov 10 01:00:00 2011
1320894000.a Wed Nov 9 22:00:00 2011
1320876000.a Wed Nov 9 17:00:00 2011
$ uname -a
SunOS dc2prcrptetl2 5.9 Generic_122300-54 sun4u sparc... (2 Replies)
Discussion started by: superparticle
2 Replies
7. Shell Programming and Scripting
Hi,
I want my unix script to run as a scheduled job such that the script is invoked once every 15 minutes. Is there any way to achieve this other than running the script as a cron job? (2 Replies)
Discussion started by: vignesh53
2 Replies
8. Shell Programming and Scripting
i have a job scheduled in crontab. The problem is, it is not running automatically as per the time scheduled. But runs when executed manually. What would be the problem? Help me with this please. (6 Replies)
Discussion started by: Santhosh CJ
6 Replies
9. UNIX for Beginners Questions & Answers
Team,
Hope you all are doing fine
I have one admin server which is being used dedicately to run cron jobs on hourly basis, fetching the details from Database which is in a different server.These cronjob are run on every hourly/5 minutes basis depending as per end user requirement.The script... (12 Replies)
Discussion started by: whizkidash
12 Replies
LEARN ABOUT OPENDARWIN
ipl
IPL(4) Kernel Interfaces Manual IPL(4)
NAME
ipl - IP packet log device
DESCRIPTION
The ipl pseudo device's purpose is to provide an easy way to gather packet headers of packets you wish to log. If a packet header is to be
logged, the entire header is logged (including any IP options - TCP/UDP options are not included when it calculates header size) or not at
all. The packet contents is also logged after the header.
Prepending every packet header logged is a structure containing information relevant to the packet following and why it was logged. The
structure's format is as follows:
struct ipl_ci {
u_long sec; /* time when the packet was logged */
u_long usec;
u_long plen; /* length of packet data logged */
u_short hlen; /* length of headers logged */
u_short rule; /* rule number (for log ...) or 0 if result = log */
u_long flags:24; /* XXX FIXME do we care about the extra bytes? */
#if (defined(OpenBSD) && (OpenBSD <= 1991011) && (OpenBSD >= 199606))
u_long filler:8; /* XXX FIXME do we care? */
u_char ifname[IFNAMSIZ];
#else
u_long unit:8;
u_char ifname[4];
#endif
};
In the case of the header causing the buffer to finish on a non-32bit
boundary, padding will be `appended' to ensure that the next log entry
is aligned to a 32bit boundary.
If the packet contents is more then 128 bytes, then only 128 bytes of the
packet contents is logged. Should the packet contents finish on a non-32bit
boundary, then the last few bytes are not logged to ensure the log entry
is aligned to a 32bit boundary.
ipl is a read-only (sequential) character pseudo-device.
The ioctls which are loaded with this device can be found under ipf(4).
The only ioctl which is used for logging and doesn't affect the filter is:
ioctl(fd, SIOCIPFFB, int *)
This ioctl flushes the log buffer and returns the number of bytes flushed.
There is currently no support for non-blocking IO with this device, meaning all read operations should be considered blocking in nature (if
there is no data to read, it will sleep until some is made available).
SEE ALSO
ipf(4)
BUGS
Packet headers are dropped when the internal buffer (static size) fills.
FILES
/dev/ipl0
IPL(4)