Sponsored Content
Top Forums Shell Programming and Scripting How to avoid running duplicated task? Post 302930835 by DGPickett on Wednesday 7th of January 2015 03:51:31 PM
Old 01-07-2015
You can run 'fuser' on the executable file to see who is running it.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

killing and relaunching a task every 15 minutes while a script is running

Hi there, I would like to write a script which while running will kill and then execute again a task every 15 minutes. Here's what I want to do: Al Jazeera English have a low quality, time-limited 15 minute trial stream up at their site. I.e. when I click on the 56K link, it will play in... (0 Replies)
Discussion started by: ropers
0 Replies

2. UNIX for Dummies Questions & Answers

Running UNIX commands remotely in Windows box from Unix box – avoid entering password

I am able to run the UNIX commands in a Windows box from a UNIX box through "SSH" functionality. But whenever the SSH connection is established between UNIX and Windows, password for windows box is being asked. Is there a way to avoid asking password whenever the SSH connection is made? Can I... (1 Reply)
Discussion started by: D.kalpana
1 Replies

3. UNIX for Advanced & Expert Users

Can root ID be duplicated

Hi, I have the root id and the uid is always 0 for the root. Can i create another user say admin with the uid as 0? If so will it have the same privilege as that of user. Will there be any effect while doing this? lorcan (6 Replies)
Discussion started by: lorcan
6 Replies

4. Shell Programming and Scripting

comment and Uncomment single task out of multiple task

I have a file contains TASK gsnmpproxy { CommandLine = $SMCHOME/bin/gsnmpProxy.exe } TASK gsnmpdbgui { CommandLine = $SMCHOME/bin/gsnmpdbgui.exe I would like to comment and than uncomment specific task eg TASK gsnmpproxy Pls suggest how to do in shell script (9 Replies)
Discussion started by: madhusmita
9 Replies

5. Shell Programming and Scripting

Parse an XML task list to create each task.xml file

I have an task definition listing xml file that contains a list of tasks such as <TASKLIST <TASK definition="Completion date" id="Taskname1" Some other <CODE name="Code12" <Parameter pname="Dog" input="5.6" units="feet" etc /Parameter> <Parameter... (3 Replies)
Discussion started by: MissI
3 Replies

6. Shell Programming and Scripting

Avoid script running multiple times by filelock

Sometimes we need a single instance of a script to run at a time. Meaning, the script itself should detects whether any instances of himself are still running and act accordingly. When multiple instances of one script running, it’s easy to cause problems. I’ve ever seen that about 350 instances... (4 Replies)
Discussion started by: edenCC
4 Replies

7. Shell Programming and Scripting

Help with remove duplicated content

Input file: hcmv-US25-2-3p hsa-3160-5 hcmv-US33 hsa-47 hcmv-UL70-3p hsa-4508 hcmv-UL70-3p hsa-4486 hcms-US25 hsa-360-5 hcms-US25 hsa-4 hcms-US25 hsa-458 hcms-US25 hsa-44812 . . Desired Output file: hcmv-US25-2-3p hsa-3160-5 hcmv-US33 hsa-47 hcmv-UL70-3p hsa-4508 hsa-4486... (3 Replies)
Discussion started by: perl_beginner
3 Replies

8. UNIX for Dummies Questions & Answers

Duplicated UID

Hi folks! I need you help to discover what's the impact of a duplicated UID in an operating system. What's the meaning when someone put in different users the same UID? (3 Replies)
Discussion started by: phcostabh
3 Replies

9. Shell Programming and Scripting

Running the calling script/task as per day

Hello all.. i have few task to do on specific day ar per weekday or weekend... for example i have 3 tasks: task1 task2 task3 Now i need to create a shell script If it is weekday it will change the status of these tasks as below sendevent -E CHANGE_STATUS -s SUCCESS -J task1... (4 Replies)
Discussion started by: j_panky
4 Replies

10. Shell Programming and Scripting

Avoid running unnecessary repetitive ps command

i have the following code: APIDS=$(echo $(ps -ef | awk -v gpid="${gpid}" '$2 == gpid || $3 == gpid {print $2,$3}') | sed 's~ ~|~g') AllProcs=$(ps -ef | awk -v allpids="${APIDS}" '$2 ~ allpids || $3 ~ allpids {print $0}' | sed '/^$/d') it seems the above... (6 Replies)
Discussion started by: SkySmart
6 Replies
fuser(8)						      System Manager's Manual							  fuser(8)

NAME
fuser - Lists process IDs of processes that are using one or more files or file structures SYNOPSIS
/usr/sbin/fuser [-cfu] file ... [Tru64 UNIX] The following format shows extensions not included in the XCU specification for this utility: /usr/sbin/fuser [-cdfku] [-h] [-vH] file ... STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: fuser: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. FLAGS
Identifies file as a mount point. In this case, fuser reports on any files that are open in the mounted file system. Report any refer- enced files that have been deleted including the referencing PID and the block count for the file in 512 byte block units. Requests a report only for the specified files. If a specified file is a mount point, fuser reports only on that file, not on any files below it. [Tru64 UNIX] Suppresses column headings in fuser output when used with the -v flag. [Tru64 UNIX] Directs fuser to display information about its command-line options. [Tru64 UNIX] Directs fuser to send a SIGKILL signal to each process. Because this flag spawns a kill operation for each process, the kill messages may not show up immediately. Directs fuser to show the user login name, in parentheses, associated with each process ID. [Tru64 UNIX] Directs fuser to display results in verbose form. PARAMETERS
[Tru64 UNIX] Directs fuser to ignore previous flag settings for the next set of file parameters. The - operand allows you to apply differ- ent flags to different sets of files in the same command line. Specifies the pathname of the file or the mount point of the file system on which fuser reports. DESCRIPTION
The fuser utility writes to standard output the process IDs of processes that are running on the local system and have one or more files or file structures in use. The utility writes to standard error additional information about these resources that indicates how each resource is being used. If file identifies a block special device, fuser lists all processes using any file on that device. This utility does not display information about files for which you do not have the appropriate privileges. For information on many files, root privilege may be required. Furthermore, you must have appropriate privileges to use the -k flag. The utility uses the following format to write the process ID for each process using each file: "%d", process_id The fuser utility writes diagnostic messages to standard error. In addition, the utility writes the following information to standard error: The pathname of each file, immediately followed by a colon. For each process ID written to standard output, one of the following characters: If the process is using the file as its current directory. [Tru64 UNIX] If the process is using a memory-mapped file. [Tru64 UNIX] If the process is using the file as the parent of its current directory. If the process is using the file as its root directory. [Tru64 UNIX] If the process has the file open. [Tru64 UNIX] If the process is using the file as its controlling tty. [Tru64 UNIX] If the process is using the text file as an executable. If you specify the -u flag, characters indicating the use of the file are followed immediately by the user name, in parentheses, that corresponds to the process's real user ID. If the user name cannot be resolved from the process's real user ID, the process's real user ID is written instead of the user name. When standard output and standard error are directed to the same file, the utility intersperses output so that the file appears at the start of each line, followed by the process ID and the characters indicating file use. Then, if the -u option is specified, the utility writes the user name or user ID for each process that is using that file. The utility writes a newline character at the end of output for each file. ENVIRONMENT VARIABLES
The following environment variables affect this utility: Provides a default value for the locale variables that are unset or null. If LANG is unset or null, the corresponding value from the POSIX (C) locale is used. If any of the locale variables contain an invalid setting, the utility behaves as if none of the variables had been set. If set to a non-empty string value, overrides the values of all the other locale variables. Specifies the locale used to interpret sequences of bytes of text data as characters (for example, determines whether arguments contain single-byte or multibyte characters). Specifies the locale that affects the format and contents of diagnostic messages written to standard error. Determines the location of message catalogs for the processing of LC_MESSAGES. NOTES
[Tru64 UNIX] The fuser utility may not report on processes that begin using a file while the utility is running. Furthermore, processes that fuser reports are using a file may have stopped using it while the utility was running. EXAMPLES
The following command lists the process IDs of processes using the /etc/hosts file: fuser /etc/hosts The following command writes to standard output the process IDs of processes that are using the current directory. The command writes to standard error an indication of how those processes are using the directory and the user names associated with those processes. fuser -fu . EXIT VALUES
The fuser utility returns the following exit values: Successful completion. An error occurred. RELATED INFORMATION
Functions: fuser(2), kill(2) delim off fuser(8)
All times are GMT -4. The time now is 08:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy