Sponsored Content
Full Discussion: Unable to grep the process
Top Forums Shell Programming and Scripting Unable to grep the process Post 302987130 by MadeInGermany on Tuesday 6th of December 2016 02:11:43 AM
Old 12-06-2016
Display the processes of user1
Code:
ps -fu user1

If "sleep" is spawned by the script then look for its parent process (given in column 3).
Maybe your grep is forged?
Code:
/bin/ps -fu user1 | /bin/grep ex

grep can match its own argument in the ps list. pgrep avoids that.
Code:
pgrep -u user1 ex

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Unable to kill sleeping process

Hi, I'm trying to delete a sleeping process (parent ID is not 1) with "kill -9" command by the owner of the process (infodba) but it doesn't get killed. Is there any way of killing this process without killing the parent process or rebooting? (I'm using HP Unix B.11.11) $ ps -eflx | grep... (0 Replies)
Discussion started by: stevefox
0 Replies

2. Shell Programming and Scripting

unable to grep the following pattern

I have the following line in file1 elif ; then now if i try to grep this using following command grep -e "elif ; then" file1 it is showing nothing... how to grep such patterns (2 Replies)
Discussion started by: suri
2 Replies

3. HP-UX

Unable to kill a process

problem. (2 Replies)
Discussion started by: pvamsikr
2 Replies

4. BSD

Unable to process from lines (envelopes)

Hi, Some of the users on my freebsd server are getting the "unable to process from lines" error when accessing their mailbox. I've checked their mailbox and found that there was a blank line at the top of the mailbox. Everytime i remove it, it appears again sometime later. I've tried... (1 Reply)
Discussion started by: sc_king
1 Replies

5. Shell Programming and Scripting

grep the process id and kill all the filtered process

Hi I want to write a shell script which can find the process id's of all the process and kill them eg: ps ax | grep rv_ 3015 ? S 0:00 /home/vivek/Desktop/rv_server 3020 ? S 0:00 /home/vivek/Desktop/rv_gps 3022 ? S 0:00 /home/vivek/Desktop/rv_show ... (7 Replies)
Discussion started by: vivek_naragund
7 Replies

6. Shell Programming and Scripting

Unable to Kill the process

Hi Guys, I am unable to kill the process . and same process is running so many times. If i am trying to kill once again it restarting/kicked off again. and now i am unable to login . i am getting error message like "error -cannot fork too many process " i know when we ll get this message... (8 Replies)
Discussion started by: kartheek
8 Replies

7. UNIX for Dummies Questions & Answers

cron job is unable to process

Hi All, I have got a shell script that excutes some job and mails me the output as an attachment. While running the script manually, its perfect. when i am scheduling the job through crontab, i am getting the mail. but the attachment but this is a blank file. after the scheduler run, i can... (2 Replies)
Discussion started by: gotam
2 Replies

8. UNIX for Dummies Questions & Answers

Unable to grep

I have a file with 2 lines of code Rome is in Romeo Romeo is in Rome How do I grep, so that only last line would be the outcome. sample output Romeo is in Rome I have tried with all possible greps but its resulting in both the lines in output. Please help. (6 Replies)
Discussion started by: gotamp
6 Replies

9. Shell Programming and Scripting

Unable to do grep in a script

Hi, I am trying to grep a filename from a script after taking the file name and other variables as keyboard input .When I run the grep command with the same filename on the prompt, it runs fine, but it is either not giving me the correct output or not running at all from the script using the... (13 Replies)
Discussion started by: dsid
13 Replies

10. Shell Programming and Scripting

Unable to grep using wildcard in a file.

I wish to check if my file has a line that does not start with '#' and has 1. Listen and 2. 443 echo "Listen 443" > test.out grep 'Listen *443' test.out | grep -v '#' Listen 443 The above worked fine but when the entry changes to the below the grep fails... (2 Replies)
Discussion started by: mohtashims
2 Replies
CALIFE.AUTH(5)						      BSD File Formats Manual						    CALIFE.AUTH(5)

NAME
calife.auth -- format of the calife authorization file DESCRIPTION
The calife.auth files are files consisting of newline separated records, one per user, containing three colon (``:'') separated fields. These fields are as follows: name User's login name / @group. shell User's shell user1,user2,...,usern List of logins allowed for the user name The name field is the login used to access the computer account. The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate the fields in the user database. One alternative syntax is to use @group to specify that any user in the given group is allowed to use calife to become root. The shell field is the command interpreter the user prefers. If there is nothing in the shell field, the user's current shell as found in the (/etc/passwd) file is assumed. If the shell field is '*', then the account is considered as locked and access is denied. If the third parameter is specified, it is assumed to be the list of login the current user has the right to become. It enables use of calife for non-root only accounts. calife.auth is placed in /etc. EXAMPLE
# calife.auth-dist # # Format # # name[:shell_to_be_run][:user1,user2,usern] # fcb roberto:/bin/tcsh pb::guest,blaireau SEE ALSO
calife(1), su(1) HISTORY
A calife.auth file format appeared in DG/UX and SunOS, written for Antenne 2 in 1991. It has evolved with the extra shell specification. The login list was reintroduced in 2.7. AUTHOR
Ollivier Robert <roberto@keltia.frmug.fr.net> BSD
September 25, 1994 BSD
All times are GMT -4. The time now is 10:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy