Sponsored Content
Full Discussion: Running scripts via su
Top Forums Shell Programming and Scripting Running scripts via su Post 302286506 by otheus on Wednesday 11th of February 2009 09:48:55 AM
Old 02-11-2009
Since you are not understanding my posts, I will let someone else help you.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Running scripts parallely

Hi, Posting my first query in this Forum,here's my query i want to execute 100 .sql files in unix having some code for connecting with db and executing procedures inside that,that to be run parallel like threads.want to run all the 100 .sql files simultanously. thanks in advance. (4 Replies)
Discussion started by: santho
4 Replies

2. UNIX for Dummies Questions & Answers

scripts running under different users

what command can i use to tell if a script is running under different users? (1 Reply)
Discussion started by: csnewbie
1 Replies

3. UNIX for Dummies Questions & Answers

Running scripts from home

I have created a Bourne shell script that helps with metric counting and it has to be run in a ClearCase view. It has been placed in a directory where if User A cd'd to it and runs it, a bunch of errors occur. Because this is a tool that several users would want access to and the program assumes... (2 Replies)
Discussion started by: mastachef
2 Replies

4. Shell Programming and Scripting

Running scripts unattended

Hi guys just wondering how i could make one of my scripts run unattended without the use of cron? (3 Replies)
Discussion started by: musicmancanora
3 Replies

5. UNIX for Dummies Questions & Answers

Automatically Running Scripts

Can someone advise me how to get started automatically running scripts? I believe it has something to do with cron? (4 Replies)
Discussion started by: jeffreydavisjr
4 Replies

6. Shell Programming and Scripting

Running scripts within scripts from cron

Hi all, I have set up a cron job which calls another shell script shell script which in turn calls a Java process. The cron tab looks so. 0,30 7-18 * * 1-5 /u01/home/weblogic/brp/bin/checkstatus.sh >> /u01/home/weblogic/logs/checkstatus.log The checkstatus.sh scripts looks like this. ... (4 Replies)
Discussion started by: sirbrian
4 Replies

7. Shell Programming and Scripting

Running 2 scripts one after the other using cron

I would like to run two scripts using cron one immediately after the other. Is it enough to put them one after another in the cron file to run at the same time, or will this cause them to run concurrently? (4 Replies)
Discussion started by: 3210
4 Replies

8. Shell Programming and Scripting

running scripts in minicom

Hi, I am new to use minicom. I want script to run on minicom with username and password as automated.(Expect). please could anyone suggest the sample code for it. Thanks in advance (2 Replies)
Discussion started by: vanid
2 Replies

9. Solaris

running scripts from cron

I need to run a script (from cron) that runs a second script. What worries me is that second script, when run from bash, upon finishing doesn't return to bash unless I press the 'Enter' key. I presume that's because last command in that script ends with & Could that be a problem for cron?... (2 Replies)
Discussion started by: orange47
2 Replies

10. Shell Programming and Scripting

Running scripts from a list

I am writing a bash script to run test some scripts. The names scripts of the scripts to tests are stored in an array. scptArr='chcksfrd.bash' scptArr='compute-misfit.bash' scptArr='compute-travel-times.bash' scptArr='create-data-tinv.bash' scptArr='create-docs.bash' ... (3 Replies)
Discussion started by: kristinu
3 Replies
PSIGNAL(9)						   BSD Kernel Developer's Manual						PSIGNAL(9)

NAME
psignal, pgsignal, gsignal -- post signal to a process or process group SYNOPSIS
#include <sys/types.h> #include <sys/signalvar.h> void psignal(struct proc *p, int signum); void pgsignal(struct pgrp *pgrp, int signum, int checkctty); void gsignal(int pgid, int signum); DESCRIPTION
These functions post a signal to one or more processes. The argument signum common to all three functions should be in the range [1-NSIG]. The psignal() function posts signal number signum to the process represented by the process structure p. With a few exceptions noted below, the target process signal disposition is updated and is marked as runnable, so further handling of the signal is done in the context of the target process after a context switch. Note that psignal() does not by itself cause a context switch to happen. The target process is not marked as runnable in the following cases: o The target process is sleeping uninterruptibly. The signal will be noticed when the process returns from the system call or trap. o The target process is currently ignoring the signal. o If a stop signal is sent to a sleeping process that takes the default action (see sigaction(2)), the process is stopped without awakening it. o SIGCONT restarts a stopped process (or puts them back to sleep) regardless of the signal action (e.g., blocked or ignored). If the target process is being traced psignal() behaves as if the target process were taking the default action for signum. This allows the tracing process to be notified of the signal. The pgsignal() function posts signal number signum to each member of the process group described by pgrp. If checkctty is non-zero, the sig- nal will be posted only to processes that have a controlling terminal. pgsignal() is implemented by walking along the process list headed by the field pg_members of the process group structure pointed at by pgrp and calling psignal() as appropriate. If pgrp is NULL no action is taken. The gsignal() function posts signal number signum to each member of the process group identified by the group id pgid. gsignal() first finds the group structure associated with pgid, then invokes pgsignal() with the argument checkctty set to zero. If pgid is zero no action is taken. SEE ALSO
sigaction(2), signal(9), tsleep(9) BSD
June 22, 1996 BSD
All times are GMT -4. The time now is 08:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy