Sponsored Content
Full Discussion: How to restart a CRON
Top Forums UNIX for Dummies Questions & Answers How to restart a CRON Post 302129104 by ddrivera on Saturday 28th of July 2007 09:22:01 AM
Old 07-28-2007
Could you just give me a general how to.
 

9 More Discussions You Might Find Interesting

1. Linux

How do cron restart on unix Tru64?

hi all, How do cron restart on unix Tru64? because don't run my cron jobs. few days age it's running fine. I did below steps: 1. cd /usr/sbin 2. cron stop response: "! Cron is already running. Exiting... Tue Nov 27 14:38:00 2007" 3. cron start response: "! Cron is already running.... (2 Replies)
Discussion started by: Tlg13team
2 Replies

2. Linux

How do cron restart on unix Tru64?

hi all, How do cron restart on unix Tru64? because don't run my cron jobs. few days age it's running fine. I did below steps: 1. cd /usr/sbin 2. cron stop responce: "! Cron is already running. Exiting... Tue Nov 27 14:38:00 2007" 3. cron start responce: "! Cron is already running.... (2 Replies)
Discussion started by: Tlg13team
2 Replies

3. AIX

AIX and cron logs filtering ?: /etc/cronlog.conf, /var/adm/cron/log

Hi, I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool... (0 Replies)
Discussion started by: Keith Johnson
0 Replies

4. UNIX for Dummies Questions & Answers

How to restart CRON file?

Hi How can I restart the CRON manually? Thanks (1 Reply)
Discussion started by: biot
1 Replies

5. Solaris

User entry in both cron.allow and cron.deny

Hello All, Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab??? Thanks in advance Vaisakh (5 Replies)
Discussion started by: ksvaisakh
5 Replies

6. Shell Programming and Scripting

Cron won't restart rsyslog

Howdy, I am nearly tearing my hair out as Cron isn't running a script that should work. I am interning for a company. Their rsyslog keeps track of traffic that gets past a firewall. It creates two files called pix.log and pix2.log. Every time something happens with the firewall, it adds to... (11 Replies)
Discussion started by: sstrahm001
11 Replies

7. Shell Programming and Scripting

Commented cron job -- cron monitoring

Hi I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies

8. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

Hi, 1) If some job supposed to run on 1st of every month at 7 AM In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day? 2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct) And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies

9. UNIX for Dummies Questions & Answers

Execution problem with Cron: Script works manually but not w/Cron. Why?

Hello gurus, I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup is shown below: #!/bin/ksh db2... (3 Replies)
Discussion started by: okonita
3 Replies
POSIX_FALLOCATE(3)					     Linux Programmer's Manual						POSIX_FALLOCATE(3)

NAME
posix_fallocate - allocate file space SYNOPSIS
#include <fcntl.h> int posix_fallocate(int fd, off_t offset, off_t len); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): posix_fallocate(): _POSIX_C_SOURCE >= 200112L DESCRIPTION
The function posix_fallocate() ensures that disk space is allocated for the file referred to by the file descriptor fd for the bytes in the range starting at offset and continuing for len bytes. After a successful call to posix_fallocate(), subsequent writes to bytes in the specified range are guaranteed not to fail because of lack of disk space. If the size of the file is less than offset+len, then the file is increased to this size; otherwise the file size is left unchanged. RETURN VALUE
posix_fallocate() returns zero on success, or an error number on failure. Note that errno is not set. ERRORS
EBADF fd is not a valid file descriptor, or is not opened for writing. EFBIG offset+len exceeds the maximum file size. EINTR A signal was caught during execution. EINVAL offset was less than 0, or len was less than or equal to 0, or the underlying filesystem does not support the operation. ENODEV fd does not refer to a regular file. ENOSPC There is not enough space left on the device containing the file referred to by fd. ESPIPE fd refers to a pipe. VERSIONS
posix_fallocate() is available since glibc 2.1.94. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +------------------+---------------+-------------------------+ |Interface | Attribute | Value | +------------------+---------------+-------------------------+ |posix_fallocate() | Thread safety | MT-Safe (but see NOTES) | +------------------+---------------+-------------------------+ CONFORMING TO
POSIX.1-2001. POSIX.1-2008 says that an implementation shall give the EINVAL error if len was 0, or offset was less than 0. POSIX.1-2001 says that an implementation shall give the EINVAL error if len is less than 0, or offset was less than 0, and may give the error if len equals zero. NOTES
In the glibc implementation, posix_fallocate() is implemented using the fallocate(2) system call, which is MT-safe. If the underlying filesystem does not support fallocate(2), then the operation is emulated with the following caveats: * The emulation is inefficient. * There is a race condition where concurrent writes from another thread or process could be overwritten with null bytes. * There is a race condition where concurrent file size increases by another thread or process could result in a file whose size is smaller than expected. * If fd has been opened with the O_APPEND or O_WRONLY flags, the function fails with the error EBADF. In general, the emulation is not MT-safe. On Linux, applications may use fallocate(2) if they cannot tolerate the emulation caveats. In general, this is only recommended if the application plans to terminate the operation if EOPNOTSUPP is returned, otherwise the application itself will need to implement a fallback with all the same problems as the emulation provided by glibc. SEE ALSO
fallocate(1), fallocate(2), lseek(2), posix_fadvise(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 POSIX_FALLOCATE(3)
All times are GMT -4. The time now is 06:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy