Locking a file when using VI to prevent multiple-edit sessions by diff users


 
Thread Tools Search this Thread
Operating Systems AIX Locking a file when using VI to prevent multiple-edit sessions by diff users
# 15  
Old 11-23-2006
Can VIM be installed on AIX 64Bit v5.2 ?

If so, can we download a package for it and where ?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Find number of ACTIVE SSH putty sessions, excluding where the user hopped on to a diff server

Hi - If iam logged on to server A, on 4 putty windows using SSH ... and out of these 4 logged-in sessions, in one of the sessions if i did SSH from server A to server B; i would now have 4 putty windows sessions ... of which 3 are actively logged on to Server A while 1 putty window is actively... (2 Replies)
Discussion started by: i4ismail
2 Replies

2. AIX

Telnet sessions stay as idle users

Hi The telnet sessions stay as idle users. It is not getting kicked out. Please advise what could be the issue. only when we reboot the server these telnet sessions goes. Below is the current output from the server. we rebooted the server three days ago: pmut6:/> uptime 04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies

3. Shell Programming and Scripting

Need Help to Edit multiple column of a file

Hello Team, I want to know if there is any one liner command , using which I can edit multiple column of a file. input file input.txt (comma separated), taran, 12.45, uttam, 23.40, babay karan, 12.45, raju, 11.40, rahulg I want to update, 2nd and 4th column, but want all those column... (8 Replies)
Discussion started by: Uttam Maji
8 Replies

4. HP-UX

Users getting kicked out of sessions

We have an old (11.11) HP-UX system. A couple of months ago, our customers started having problems with their logins. After sitting idle for roughly an hour, their screens would lock up and they would be kicked out of the system. This happens if they are in the application or on the command... (2 Replies)
Discussion started by: slkdnichols
2 Replies

5. UNIX for Dummies Questions & Answers

In vi, any way to prevent :edit from repositioning the screen?

I am working on a project where I need to make many changes to files, both inside and outside of the vi editor. I make small changes manually right in vi, and I have a script that I run from another session that I use to make bigger changes to the files using sed. After running my script from... (2 Replies)
Discussion started by: RickS
2 Replies

6. UNIX for Advanced & Expert Users

Samba - prevent locking of selected files over network?

I have a samba server which is serving a mixture of files. One main application uses a data file and creates a temporary working execution file at startup and holds that temp execution file open for the duration of the program's execution (but doesn't use the file at all after initial startup). ... (0 Replies)
Discussion started by: humbletech99
0 Replies

7. Solaris

locking a users file as root

hello, I have a challenge to find a way to lock down a file in a user's home directory, such that a user can NOT modify, rename, move, delete, etc. The solution needs to be deployable without, for example, having to switch from unix to windows, etc We are using NFS. We want to lock the... (1 Reply)
Discussion started by: jvmagic
1 Replies

8. Solaris

Prevent users logging in as root

I would like to know how to prevent users connecting to a server using SSH as root. I would still like them to be able to login with their username and then change to su. But I would like to prevent them logging in directly as root. I have searched the forum and read that I should set... (3 Replies)
Discussion started by: Sepia
3 Replies

9. AIX

Users Are Getting Kicked out of 2Hr Sessions

:confused:We've had close to 100 calls about users logging into our AIX server. The users open up about 3 to 5 sessions in the server. After 2hrs of idle time, users are frozen or stuck in the IBM UniVerse Application. We (system administrators) have been blaming the application (which we'll take... (2 Replies)
Discussion started by: Sarccastik Dude
2 Replies

10. Shell Programming and Scripting

Prevent file from being mailed multiple times from a job

We have a ksh which runs once every 15 minutes. Based on a certain condition (for invalid data) we are spooling a file and if the file is of length greater than 0 bytes, then we are mailing this file to a group of users. Upon receiving the file, users correct the data so that on its next run the... (2 Replies)
Discussion started by: Sree_2503
2 Replies
Login or Register to Ask a Question
edit-pr(1)                                                     GNATS User Utilities                                                     edit-pr(1)

NAME
edit-pr - edit a problem report in the GNATS database SYNOPSIS
edit-pr [ -h | --help ] [ -V | --version ] [ -d databasename | --database=databasename ] [ -H host | --host=host ] [ -P port | --port=port ] [ -v user | --user=user ] [ -w password | --passwd=password ] PR DESCRIPTION
edit-pr is used to make changes to existing PRs in a GNATS database. edit-pr first examines the PR and locks it if it is not already locked. This is to prevent a PR from being edited by two users simultane- ously. If the PR is already in the process of being edited, edit-pr displays the name of the person who owns the lock. edit-pr then calls $EDITOR on PR. After the PR has been edited, it is resubmitted to the database, and the index is updated. If you change a field that requires a reason for the change, edit-pr prompts you to supply a reason for the change. A message is then ap- pended to the Audit-Trail field of PR with the changed values and the change reason. Depending on how the database is configured, editing various fields in the PR may also cause mail to be sent concerning these changes. In the default configuration, any fields that generate Audit-Trail entries will cause a copy of the new Audit-Trail message to be sent. OPTIONS
-h, --help Prints a brief usage message for edit-pr. -V, --version Prints the version number for edit-pr. -d, --database Specifies the database containing the PR to be edited; if no database is specified, the database named default is assumed. This option overrides the database specified in the GNATSDB environment variable. GNATS network options: -H, --host Hostname of the GNATS server. -P, --port The port that the GNATS server runs on. -v, --username Username used to log into the GNATS server. -w, --passwd Password used to log into the GNATS server. ENVIRONMENT VARIABLES
The environment variable EDITOR specifies the editor to invoke on the PR. Default is vi(1). The GNATSDB environment variable is used to determine which database to use. For a local database, it contains the name of the database to access. For network access via gnatsd, it contains a colon-separated list of strings that describe the remote database, in the form server:port:databasename:username:password Any of the fields may be omitted, but at least one colon must appear; otherwise, the value is assumed to be the name of a local database. If GNATSDB is not set, it is assumed that the database is local and that its name is default. FILES
/tmp/ep$$ Temporary file for PR being edited. /tmp/ed_pr_ch$$ Holds Audit-Trail change message, if needed. /tmp/u$$ Holds output of lock function. SEE ALSO
Keeping Track: Managing Messages With GNATS (also installed as the GNU Info file gnats.info) databases(5), dbconfig(5), delete-pr(8), edit-pr(1) file-pr(8), gen-index(8), gnats(7), gnatsd(8), mkcat(8), mkdb(8), pr-edit(8), query- pr(1), queue-pr(8), send-pr(1). COPYING
Copyright (c) 1993, 2003, Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. GNATS August 2003 edit-pr(1)