05-20-2008
Well answer to this is simple..!
Whenever your second script will run , it will create a lock file, say "lckfile"
Before you add statements to your log file , in the main script, you just need to check if "lckfile" exists.
If it exists , it means you are archiving or chomping your original log files and you need to append your log statements in the temp log file.
If it does not exists, you are safe to add your log statements in the orignal log files.
Hope this helps!
nua7
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Hi all,
I want to set a size limitation for some user in the system, for an example, each user only have 5MB free space in the system. The user cannot user more than 5 MB space.
Is it possible to do this? Thanks! (1 Reply)
Discussion started by: felix_koo
1 Replies
2. HP-UX
Hi All,
Can anyone please clarify me the following questions:
1. Is there any file size limitation in HP-UX 11i, that I can able to create upto certain size of file (say 2 GB) and not more then that????
2. At max. how many files we can able to keep inside a folder????
3. How many... (2 Replies)
Discussion started by: sundeep_mohanty
2 Replies
3. Shell Programming and Scripting
hi ,
iam trying to sort millions of records which is delimited and i cant able to
use sort command more than 60 million..if i try to do so i got an message stating that "File size limit exceeded",Is there any file size limit for using sort command..
How can i solve this problem.
thanks
... (7 Replies)
Discussion started by: cskumar
7 Replies
4. Linux
Hi
I am trying to rcp a file from Solaris box to Linux.
When the file size is 2,205,255,047, the rcp fails with the message
Jan 10 01:11:53 hqsas167 rsh: pam_authenticate: error Authentication failed
However when I rcp a file with smaller size - 9,434,477 - the rcp completes with... (2 Replies)
Discussion started by: schoubal
2 Replies
5. Shell Programming and Scripting
Hi to every body there,
I am new this forum and this is my first post.
I am a new user of Unix,
is there any size limitation of files while creating tar file.
Thanks in advance (4 Replies)
Discussion started by: Manvar Khan
4 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I ran code in test environment to find the files more than 1TB given below is a snippet from code:
FILE_SYSTEM=/home/arun
MAX_FILE_LIMIT=1099511627776
find $FILE_SYSTEM -type f -size +"$MAX_FILE_LIMIT"c -ls -xdev 2>/dev/null |
while read fname
do
echo "File larger than... (3 Replies)
Discussion started by: Arunprasad
3 Replies
7. Solaris
Hello All,
I am using a SunOS machine. My application creates output files for the downstream systems. However output files are restricted to 2GB of file size in SunOS due to which I am forced to create multiple files which is not supported by the downstream due to some limitations.
Is... (5 Replies)
Discussion started by: pasupuleti81
5 Replies
8. UNIX for Advanced & Expert Users
Hello
first, truth been told, I'm not even close to be advanced user. I'm posting here because maybe my question is complicated enough to need your expert help
I need to use awk (or nawk - I don't have gawk) to validate some files by computing the total sum for a large numeric variable.
It... (1 Reply)
Discussion started by: cwitarsa
1 Replies
9. Linux
Hi friends,
I tried to take a backup of my PC using tar command. But it ended with an error
tar: /home/backup/back.tar.gz: Cannot write: No space left on device
tar: Error is not recoverable: exiting now
But i checked the disk space and there is enough space is available.
]# df
Filesystem... (11 Replies)
Discussion started by: siva3492
11 Replies
10. Linux
Hello Friends,
I tried to take tar backup in my server, but it ended with an error.
It said that:
/home/back/pallava_backup/fbackup_backup/stape_config
/home/back/romam_new.tar.gz
tar: /home/backup/back.tar.gz: Cannot write: No space left on device
tar: Error is not recoverable: exiting... (10 Replies)
Discussion started by: siva3492
10 Replies
LEARN ABOUT MOJAVE
shlock
SHLOCK(1) BSD General Commands Manual SHLOCK(1)
NAME
shlock -- create or verify a lock file for shell scripts
SYNOPSIS
shlock [-du] [-p PID] -f lockfile
DESCRIPTION
The shlock command can create or verify a lock file on behalf of a shell or other script program. When it attempts to create a lock file, if
one already exists, shlock verifies that it is or is not valid. If valid, shlock will exit with a non-zero exit code. If invalid, shlock
will remove the lock file, and create a new one.
shlock uses the link(2) system call to make the final target lock file, which is an atomic operation (i.e. "dot locking", so named for this
mechanism's original use for locking system mailboxes). It puts the process ID ("PID") from the command line into the requested lock file.
shlock verifies that an extant lock file is still valid by using kill(2) with a zero signal to check for the existence of the process that
holds the lock.
The -d option causes shlock to be verbose about what it is doing.
The -f argument with lockfile is always required.
The -p option with PID is given when the program is to create a lock file; when absent, shlock will simply check for the validity of the lock
file.
The -u option causes shlock to read and write the PID as a binary pid_t, instead of as ASCII, to be compatible with the locks created by
UUCP.
EXIT STATUS
A zero exit code indicates a valid lock file.
EXAMPLES
BOURNE SHELL
#!/bin/sh
lckfile=/tmp/foo.lock
if shlock -f ${lckfile} -p $$
then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
fi
C SHELL
#!/bin/csh -f
set lckfile=/tmp/foo.lock
shlock -f ${lckfile} -p $$
if ($status == 0) then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
endif
The examples assume that the file system where the lock file is to be created is writable by the user, and has space available.
HISTORY
shlock was written for the first Network News Transfer Protocol (NNTP) software distribution, released in March 1986. The algorithm was sug-
gested by Peter Honeyman, from work he did on HoneyDanBer UUCP.
AUTHORS
Erik E. Fair <fair@clock.org>
BUGS
Does not work on NFS or other network file system on different systems because the disparate systems have disjoint PID spaces.
Cannot handle the case where a lock file was not deleted, the process that created it has exited, and the system has created a new process
with the same PID as in the dead lock file. The lock file will appear to be valid even though the process is unrelated to the one that cre-
ated the lock in the first place. Always remove your lock files after you're done.
BSD
June 29, 1997 BSD