Hi,
Does anyone seen this error before..
kernel: ENOMEM in journal_alloc_journal_head, retrying.
I encounter this problem on IBM eServers where when the above error appears usually the machine is dead or hanged. Unless a hard reboot is been done. Is this something have to do with the memory... (1 Reply)
hi #!/bin/bash
SERVER=10.89.40.35
USER=xyz
PASSWD=xyz
ftp -in $SERVER<<EOF
user $USER $PASSWD
mkdir PPL
cd /path of remote dir
lcd /path of local dir
hash
bin
put <file name>
bye
<<EOF
The above ftp script i have to schedule in crontab at a particular instance of time run daily.... (2 Replies)
I am using the following code in a C Shell script to transfer files to a remote server:
ftp -n logxx.xxxx.xxx.xxx.com <<DO_FTP1
quote user $user_name
quote pass $password
ascii
put $js_file_name
bin
put $FinalZipFile
quit
DO_FTP1
This code works great except on those rare occasions... (8 Replies)
ok, so I'm trying to add a function to my local script that runs a command on a remote host. The reason why this is needed is that, there are other scripts that run different commands on the same remote host.
so the problem is that many times there are multiple scripts being run on the remote... (1 Reply)
hi, everyone.
My want to execute the shell script below per 10 seconds
PID=`pgrep java`
if
then
/home/java/java
fi
crontab wouldn't help me.
some one can give me suggestions?thanks
---------- Post updated at 07:29 AM ---------- Previous update was at 07:26 AM ----------
... (6 Replies)
Hi ,
When i hit the URL using WGET command ,it is retrying according to the number of retry we mentioned along with Wget command.
my expectation :
1) If 1st try is failed and iam retrying again before 2nd retry i have to check for "xxxxxxx" entry in the log file.
2) If "XXXXXXX" entry is... (4 Replies)
Hi,
I am new to this forum, could any one please help me to understand the LOCKFILE command with an example and what exactly it is used for and how it is used.
Thanks
Reshu289 (4 Replies)
I need to read a file line by line, then depending on the contents of each line, type in a code that will get written to an array.
The problem I have is when I ask the user to confirm the input code, if it is wrong, how do i Return to ask again?
Any thing I try increments the file to the next... (6 Replies)
Hi,
I have a process which can run one instance at a time. Currently we have multiple scripts trying to kickoff this process. I wanted to implement the semaphore mechanism to achieve this.
I was going through few examples. The below code seems to be reasonable solution.
... (5 Replies)
We encountered these error 2 times(e.g. Solaris 10 with NetWorker installed) with in the month of August, but we couldn't pin point the root cause, it might be bad sector, bad cable or software incompatibility?
Do you experience these issue or please share your understanding about this? Thanks... (0 Replies)
Discussion started by: B@S
0 Replies
LEARN ABOUT LINUX
dotlockfile
DOTLOCKFILE(1) Cistron Utilities DOTLOCKFILE(1)NAME
dotlockfile - Utility to manage lockfiles
SYNOPSIS
/usr/bin/dotlockfile [-l [-r retries] |-u|-t|-c] [-p] [-m|lockfile]
DESCRIPTION
dotlockfile is a command line utility to reliably create, test and remove lockfiles. It creates lockfiles reliably on local and NFS
filesystems, because the crucial steps of testing for a preexisting lockfile and creating it are performed atomically by a single call to
link(2). Manpage lockfile_create(3) describes the used algorithm.
dotlockfile is installed with attribute SETGID mail and thus can also be used to lock and unlock mailboxes even if the mailspool directory
is only writable by group mail.
The name dotlockfile comes from the way mailboxes are locked for updates on a lot of UNIX systems. A lockfile is created with the same
filename as the mailbox but with the string ".lock" appended.
The names dotlock and lockfile were already taken - hence the name dotlockfile :).
OPTIONS -l Create a lockfile if no preexisting valid lockfile is found, else wait and retry according to option -r. This option is the
default.
A lockfile is treated as valid,
o if it holds the process-id of a running process,
o or if it does not hold any process-id and has been touched less than 5 minutes ago (timestamp is younger than 5 minutes).
-r retries
The number of times dotlockfile retries to acquire the lock if it failed the first time before giving up. The initial sleep after
failing to acquire the lock is 5 seconds. After each retry the sleep intervall is increased incrementally by 5 seconds up to a
maximum sleep of 60 seconds between tries. The default number of retries is 5. To try only once, use "-r 0".
-u Remove a lockfile.
-t Touch an existing lockfile (update the timestamp). Useful for lockfiles on NFS filesystems. For lockfiles on local filesystems the
-p option is preferable.
-c For debugging only: Check for the existence of a valid lockfile.
Note: Testing for a preexisting lockfile and writing of the lockfile must be done by the same "dotlockfile -l" or "dotlockfile -m"
command, else the lockfile creation cannot be reliable.
-p Write the process-id of the calling process into the lockfile. Also when testing for an existing lockfile, check the contents for
the process-id of a running process to verify if the lockfile is still valid. Obviously useful only for lockfiles on local
filesystems.
-m Lock or unlock the current users mailbox. The path to the mailbox is the default system mailspool directory (usually /var/mail)
with the username as gotten from getpwuid() appended. If the environment variable $MAIL is set, that is used instead. Then the
string ".lock" is appended to get the name of the actual lockfile.
lockfile
The lockfile to be created or removed. Must not be specified, if the -m option is in effect.
RETURN VALUE
Zero on success, and non-zero on failure. For the -c option, sucess means that a valid lockfile is already present. When locking (the
default, or with the -l option) dotlockfile returns the same values as the library function lockfile_create(3). Unlocking a non-existant
lockfile is not an error.
NOTES
The lockfile is created exactly as named on the command line. The extension ".lock" is not automatically appended.
This utility is a lot like the lockfile(1) utility included with procmail, and the mutt_dotlock(1) utility included with mutt. However the
command-line arguments differ, and so does the return status. It is believed, that dotlockfile is the most flexible implementation, since
it automatically detects when it needs to use priviliges to lock a mailbox, and does it safely.
The above mentioned lockfile_create(3) manpage is present in the liblockfile-dev package.
BUGS
None known.
SEE ALSO lockfile_create(3), maillock(3)AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
September 8, 2009 DOTLOCKFILE(1)