and make it executable, but the username for the file isn't the one with the rights on the process ids.
Is there a way to get this file to be picked up by a script run as root and executed?
The file should be run as soon as it is fully created (like within one minute or so). What would be a better option, run through crontab, or by using a loop / lockfile?
It should be possible to create more than one of these files, so the filename should be variable.
Hi,
I scheduled one script through crontab command and seems like it is hanging. I come to know this through the command 'ps -ef' whcih is showing me the program running, but no chances of it to take more than 2hrs to comlpete.
I want to kill that process. I tried to kill it using the... (6 Replies)
Hey
I'm writing a script that creates some processes,and some scripts which kill those processes.
the question is Simply:
How can I allow a group members to be able to kill (using kill command) processes created by other user at the same group?
and i need the change to be at the script... (5 Replies)
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Hi Here is my problem:
1)I am login to unix server through my login id and do SU - xxx
2) Start the script which is running in background
I want that other user which login to there id and do SU - yyy(Different user) kill that
script.
Could you please help me in this. (9 Replies)
How can I kill a process owned by user1? I will be using another user (user2) (not root) and we are on the same primary and secondary group. I copied everything including it's .profile and set the path accordingly.
user1@hostnmae0:/home/user1 $ pkill java
pkill: Failed to signal pid 1234:... (2 Replies)
Hi!
I need your help, please.
I'm in AIX node and sometimes listener process from an oracle instance gets duplicated, i mean that it get spawned a second listener process. As we can't apply changes to the databases on this months, i want to build a shell that can identify the second... (6 Replies)
Hi folks,
I want to kill all process of oracle user and won't kill shell, should i try this? Please confirm.
1st way
pgrep -u oracle | sudo xargs kill -9
2nd way
killall -u oracle (2 Replies)
the task is grant user1 to kill another (for example user2) process. My steps:
by root:
usermod -P "Process Management" user1
login user1
user1@server (~) pfexec kill <PID>
the result is:
ksh: <PID>: not found
or user1@server (~) pfexec pkill <PID>
the result: nothing happens, still... (0 Replies)
Discussion started by: dsyberia
0 Replies
LEARN ABOUT DEBIAN
apache2::sitecontrol::user
Apache2::SiteControl::User(3pm) User Contributed Perl Documentation Apache2::SiteControl::User(3pm)NAME
Apache2::SiteControl::User - User representations
SYNOPSIS
my $user = Apache2::SiteControl->getCurrentUser($r);
# $r is the apache request object
# Checking out the user's name:
if($user->getUsername eq 'sam') { ... }
...
# Working with attributes (session persistent data)
my $ssn = $user->getAttribute('ssn');
$user->setAttribute($r, 'ssn', '333-555-6666');
# Removing/invalidating session for the user
$user->logout($r);
DESCRIPTION
The SiteControl system has a base concept of a user which includes the user's name, persistent attributes (which are persistent via
session), and support for user logout.
It is assumed that you will be working from mod_perl, and some of the methods require an Apache request object. The request object is used
by some methods to coordinate access to the actual session information in the underlying system (for storing attributes and implementing
logout).
User objects are created by a factory (by default Apache2::SiteControl::UserFactory), so if you subclass User, you must understand the
complete interaction between the factory (which is responsible for interfacing with persistence), the SiteControl, etc.
The default implementation of User and UserFactory use AuthCookie to manage the sessions, and Apache::Session::File to store the various
details about a user to disk.
If you are using Apache2::SiteControl::User and Apache::SiteControl::UserFactory (the default and recommended), then you should configure
the following parameters in your apache configuration file:
# This is where the session data files will be stored
SiteControlSessions directory_name
# This is where the locks will be stored
SiteControlLocks directory_name
These two directories should be different, and should be readable and writable by the apache daemon only. They must exist before trying to
use SiteControl.
METHODS
getUsername Get the name that the current user used to log in.
getAttribute($name) Get the value of a previously stored attribute. Returns undef is there is no value.
setAttribute($request, $name, $value) Add an attribute (scalar data only) to the current session. The current apache request object is
required (in order to figure out the session). Future versions may support more complex storage in the session. This attribute will stay
associated with this user until they log out.
logout($request) Log the user out. If you do not pass the current apache request, then this method will log an error to the apache error
logs, and the user's session will continue to exist.
SEE ALSO
Apache2::SiteControl::UserFactory, Apache::SiteControl::ManagerFactory, Apache2::SiteControl::PermissionManager, Apache::SiteControl
AUTHOR
This module was written by Tony Kay, <tkay@uoregon.edu>.
COPYRIGHT AND LICENSE
This modules is covered by the GNU public license.
perl v5.14.2 2006-03-17 Apache2::SiteControl::User(3pm)