Sponsored Content
Full Discussion: how to do file locking?
Top Forums UNIX for Dummies Questions & Answers how to do file locking? Post 302219553 by yang on Tuesday 29th of July 2008 12:32:48 PM
Old 07-29-2008
i wil lbe using shell script and ubuntu to test..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ftp file locking

I have a set of scripts to do software releases to remote machines which uses ftp. I'm having a problem getting 'lost connection' messages. What I wanted to ask is, does ftp employ some sort of file locking if two ftp processes are trying to copy the same file at the same time? & if so could... (2 Replies)
Discussion started by: Kevin Pryke
2 Replies

2. UNIX for Dummies Questions & Answers

file locking question

Hi, Simple question but I just need to confirm the answer: If two or more processes attempt to move the same file at exactly the same time, will unix internal file locking allow only one of the processes to access the file? Many thanks Helen :) (2 Replies)
Discussion started by: Bab00shka
2 Replies

3. UNIX for Dummies Questions & Answers

File Locking in Unix

Hi I would like to lock a file using korn Shell Script before coping the contents of the file. Do let me know Thanks in Advance. Senone (3 Replies)
Discussion started by: senone
3 Replies

4. UNIX for Advanced & Expert Users

File Locking

Hi, Does anyone know what happens when two processes are simultaneously trying to write to a single file in UNIX (AIX)? Cheers (1 Reply)
Discussion started by: penfold
1 Replies

5. UNIX for Dummies Questions & Answers

Locking a file in ksh

We want to lock a file, during a program(pgm1) execution(until the execution of the program is completed), so that other program(pgm2) can't read/edit that file, until execution of earlier program(pgm1) is completed. How can this be achieved thru shell scripting... we tried chmod +l option, but... (1 Reply)
Discussion started by: thanuman
1 Replies

6. UNIX for Dummies Questions & Answers

file locking

how do i implement file locking in unix? example if i want to update a file, i would like to use file locking. how do i implement it? i am using shell script thanks (3 Replies)
Discussion started by: yang
3 Replies

7. UNIX for Advanced & Expert Users

File locking

i am working on a device runnin on linux....i have configured the samba server in the device such that my windows PC can access a shared folder in the device. Also in the device i am runnin some programs which access the files in this shared folder. What i want to know is whether there is any way i... (1 Reply)
Discussion started by: abhinx
1 Replies

8. Solaris

Help with set GID File Locking

Hello, I ls -al to see the permission of a file and there is 1 file have strange permission. It's a "l" instead of "x". -rwxr-lr-x 1 root other 24905 Jan 11 2007 /etc/vx/isis/Registry.pre-ddlpro -rw-r-lr-- 1 root root 0 Jan 6 43:25... (2 Replies)
Discussion started by: Smith
2 Replies

9. UNIX for Advanced & Expert Users

NFS4 locking file question

All, Just wondering if someone has a file open on client A for writing and it is locked, is that file still readable from client A or B? Basically I'm just wanting to know if a file is opened already, can it still be opened for read only? (1 Reply)
Discussion started by: markdjones82
1 Replies

10. Emergency UNIX and Linux Support

Perl NFS file locking

Got a weird problem. I have a user that inherited a data processing system written in Perl. The system consists of about 150 Perl scripts and about 40 Fortran executables. The system had been working fine until recently, when I changed our file server configuration. First the system... (2 Replies)
Discussion started by: ccj4467
2 Replies
sponsor-patch(1)					      General Commands Manual						  sponsor-patch(1)

NAME
sponsor-patch - Prepare, test-build, and sponsor an upload. SYNOPSIS
sponsor-patch [options] bug sponsor-patch -h DESCRIPTION
sponsor-patch downloads the patch or Bazaar branch linked to an Ubuntu bug, applies it, generates a review diff, (optionally) test builds it, runs lintian(1) and, after review and confirmation, can upload it. sponsor-patch can be used for sponsoring patches, syncs and merges from Debian, SRUs, and creating debdiffs from patches. If bug has mul- tiple patches or branches linked, it will prompt the user to select one. The same applies to bug tasks. If the attached patch is not a debdiff, edit-patch(1) is used to apply it. Some obvious checks are performed, in particular: 1. update-maintainer(1) is run on the source package to ensure that the Maintainer field meets the Ubuntu policy. 2. The version number must be greater than the current version in the archive. The changes file is also correctly generated to list all changes since the current version in the archive. 3. The changelog must automatically close the sponsorship bug. 4. The changelog target must be valid. 5. The changelog timestamp is touched. Should any checks (or the build) fail, the user has an option to edit the patched source and try building it again. Unless a working directory is specified, the sources and patches will be downloaded into a temporary directory in /tmp, which is removed once the script finishes running. The output of the build tool will be placed in workdir/buildresult/. One of --upload, --workdir, or --sponsor must be specified. OPTIONS
-b, --build Build the package with the specified builder. Note for pbuilder(8) and cowbuilder(8) users: This assumes the common configuration, where the ARCH and DIST environment is read by pbuilderrc(5) to select the correct base image. -B BUILDER, --builder=BUILDER Use the specify builder to build the package. Supported are cowbuilder(8), cowbuilder-dist(1), pbuilder(8), pbuilder-dist(1), and sbuild(1). The default is pbuilder(8). -e, --edit Launch a sub-shell to allow editing of the patched source before building. -h, --help Display a help message and exit. -k KEY, --key=KEY Specify a key ID for signing the upload. -l INSTANCE, --lpinstance=INSTANCE Use the specified instance of Launchpad (e.g. "staging"), instead of the default of "production". --no-conf Do not read any configuration files, or configuration from environment variables. -s, --sponsor Shortcut for sponsored uploads. Equivalent to -b -u ubuntu. -u DEST, --upload=DEST Upload to DEST with dput(1) (after confirmation). -U, --update Update the build environment before attempting to build. -v, --verbose Print more information. -w DIR, --workdir=DIR Use the specified working directory, creating it if necessary. If WORKDIR is not specified, a temporary directory is created, which is deleted before sponsor-patch exits. ENVIRONMENT
All of the CONFIGURATION VARIABLES below are also supported as environment variables. Variables in the environment take precedence to those in configuration files. CONFIGURATION VARIABLES
The following variables can be set in the environment or in ubuntu-dev-tools(5) configuration files. In each case, the script-specific variable takes precedence over the package-wide variable. SPONSOR_PATCH_BUILDER, UBUNTUTOOLS_BUILDER The default value for --builder. SPONSOR_PATCH_LPINSTANCE, UBUNTUTOOLS_LPINSTANCE The default value for --lpinstance. SPONSOR_PATCH_UPDATE_BUILDER, UBUNTUTOOLS_UPDATE_BUILDER The default value for --update. SPONSOR_PATCH_WORKDIR, UBUNTUTOOLS_WORKDIR The default value for --workdir. SPONSOR_PATCH_KEYID, UBUNTUTOOLS_KEYID The default value for --key. EXAMPLES
Test-building and sponsoring an upload of bug 1234: sponsor-patch -s 1234 Performing a test build of bug 1234 in your PPA: sponsor-patch -u ppa:user/ppa 1234 SEE ALSO
bzr(1), debchange(1), debdiff(1), dput(1), edit-patch(1), lintian(1), cowbuilder(8), cowbuilder-dist(1), pbuilder(8), pbuilder-dist(1), sbuild(1), ubuntu-dev-tools(5), update-maintainer(1) AUTHORS
sponsor-patch was written by Benjamin Drung <bdrung@ubuntu.com>, and this manual page was written by Stefano Rivera <stefanor@ubuntu.com>. Both are released under the terms of the ISC License. ubuntu-dev-tools September 21 2010 sponsor-patch(1)
All times are GMT -4. The time now is 11:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy