Sponsored Content
Operating Systems AIX How do I killed ideal users from AIX 5.3 smit? Post 302503066 by kah00na on Wednesday 9th of March 2011 03:28:41 PM
Old 03-09-2011
I think you mean "idle" instead of "ideal".

You can write a script to search for processes older than one hour and kill them.
 

10 More Discussions You Might Find Interesting

1. What is on Your Mind?

AIX Smit menu designer. WinSmit

Hi, Please excuse me for posting an "ad" message here. Over the last few months I have created software called WinSmit, with this tool you can create your own AIX smit menus and corresponding message files. We all know the smit or smitty menus that IBM provides to maintain the system, the... (6 Replies)
Discussion started by: mimyrtek
6 Replies

2. AIX

Users on AIX 5.2

Hi everybody, I have a system with AIX 5.2. I want to create a User on this system. This User shouldn't has an admin rights, but I want to allow him to remove any directory from a specific path where the owner of this path is another user (not root). what is the properties that should be... (4 Replies)
Discussion started by: aldowsary
4 Replies

3. AIX

Users in AIX

Good Afternoon How can i change password without it requests the following thing to me: Changing password for "prueba1" prueba1's Old password: what desire is that is made directly like in root: Changing password for "prueba1" prueba1's New password: In the company have a two role... (3 Replies)
Discussion started by: Lost in AIX
3 Replies

4. UNIX for Dummies Questions & Answers

Probably an easy AIX-SMIT question with mkroute

Hi All, I am on a project and logging into about 100 servers one at a time. One of the steps I am performing is setting up a link with smit mkroute. I am using AIX versions 5.2 and 5.3 Does anyone know a quick command line to set DESTINATION ADDRESS, GATEWAY address, Network MASK, and... (5 Replies)
Discussion started by: jeffpas
5 Replies

5. Solaris

SMIT i AIX Sun Solaris ?

i now when i want use the smit in AIX is possible but a ask if you has in sun same job in sun tel me please awating supports (3 Replies)
Discussion started by: Yalmalki
3 Replies

6. Shell Programming and Scripting

Using expect script with AIX's SMIT in cron

My searches turned up nothing relevant, so I apologize if this has already been looked at. I am trying to run an expect script from a Solaris machine, that ssh's into an AIX machine, and interacts with a SMIT created menu system that runs a few backups for me. The expect script runs fine when... (0 Replies)
Discussion started by: Mariognarly
0 Replies

7. AIX

Users on Aix 6

Hello everybody My question is about which default userīs should I disable it on Aix 6.1 I would like to hear your opinions. Thanks for your comments (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

8. AIX

adding users via smit

I apologize if this is a simple/stupid question. When I add users in smit as root, many(most) of the fields are automatically popluated with some basic default values. Some other admins here have access to create users via sudo, however when they create users (sudo smit users), the user gets... (3 Replies)
Discussion started by: mshilling
3 Replies

9. AIX

AIX 5.3 Using sudo to control smit

Does anyone have any experience using sudo to control smit on AIX 5.3? These are the smit commands that I want certain users to execute: # Cmnd alias specification Cmnd_Alias SMIT = /bin/smit hacmp, \ /bin/smit pxdam, \ /bin/smit cl_lsuser, \ /bin/smit cl_users, \ /bin/smit cl_passwd ... (5 Replies)
Discussion started by: tharrieswk
5 Replies

10. AIX

What are the ideal ulimit settings for root user in AIX?

Hi, what are the ideal/best/recommended ulimit settings for a root user in AIX? I understand that it depends on our environment. But I would like to know...what are settings you guys use in your environment for best performance. default: fsize = 2097151 core = 2097151 ... (8 Replies)
Discussion started by: System Admin 77
8 Replies
MYSQLPROCGREP(1)						  MySQL Utilities						  MYSQLPROCGREP(1)

NAME
mysqlprocgrep - Search MySQL servers for processes matching a pattern SYNOPSIS
mysqlprocgrep [options] DESCRIPTION
This utility scans the process lists for the servers specified using instances of the --server option and selects those that match the con- ditions specified using the --age and --match-xxx options. For a process to match, all conditions given must match. The utility then either prints the selected processes (the default) or executes certain actions on them. If no --age or --match-xxx options are given, the utility selects all processes. The --match-xxx options correspond to the columns in the INFORMATION_SCHEMA.PROCESSLIST table. For example, --match-command specifies a matching condition for PROCESSLIST.COMMAND column values. There is no --match-time option. To specify a condition based on process time, use --age. Processes that can be seen and killed are subject to whether the account used to connect to the server has the PROCESS and SUPER privi- leges. Without PROCESS, the account cannot see processes belonging to other accounts Without SUPER, the account cannot kill processes belonging to other accounts To specify how to display output, use one of the following values with the --format option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the G command for the mysql monitor. OPTIONS
mysqlprocgrep accepts the following command-line options: --help Display a help message and exit. --age=<time> Select only processes that have been in the current state more than a given time. The time value can be specified in two formats: either using the hh:mm:ss format, with hours and minutes optional, or as a sequence of numbers with a suffix giving the period size. The permitted suffixes are s (second), m (minute), h (hour), d (day), and w (week). For example, 4h15m mean 4 hours and 15 minutes. For both formats, the specification can optionally be preceded by + or -, where + means older than the given time, and - means younger than the given time. --format=<format>, -f<format> Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. --kill-connection Kill the connection for all matching processes (like the KILL CONNECTION statement). --kill-query Kill the query for all matching processes (like the KILL QUERY statement). --match-command=<pattern> Match all processes where the Command field matches the pattern. --match-db=<pattern> Match all processes where the Db field matches the pattern. --match-host=<pattern> Match all processes where the Host field matches the pattern. --match-info=<pattern> Match all processes where the Info field matches the pattern. --match-state=<pattern> Match all processes where the State field matches the pattern. --match-user=<pattern> Match all processes where the User field matches the pattern. --print Print information about the matching processes. This is the default if no --kill-connection or --kill-query option is given. If a kill option is given, --print prints information about the processes before killing them. --regexp, --basic-regexp, -G Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. This affects the --match-xxx options. --server=<source> Connection information for a server to search in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. Use this option multiple times to search multiple servers. --sql, --print-sql, -Q Instead of displaying the selected processes, emit the SELECT statement that retrieves information about them. If the --kill-connection or --kill-query option is given, the utility generates a stored procedure named kill_processes() for killing the queries rather than a SELECT statement. --sql-body Like --sql, but produces the output as the body of a stored procedure without the CREATE PROCEDURE part of the definition. This could be used, for example, to generate an event for the server Event Manager. When used with a kill option, code for killing the matching queries is generated. Note that it is not possible to execute the emit- ted code unless it is put in a stored routine, event, or trigger. For example, the following code could be generated to kill all idle connections for user www-data: $ mysqlprocgrep --kill-connection --sql-body > --match-user=www-data --match-state=sleep DECLARE kill_done INT; DECLARE kill_cursor CURSOR FOR SELECT Id, User, Host, Db, Command, Time, State, Info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE user LIKE 'www-data' AND State LIKE 'sleep' OPEN kill_cursor; BEGIN DECLARE id BIGINT; DECLARE EXIT HANDLER FOR NOT FOUND SET kill_done = 1; kill_loop: LOOP FETCH kill_cursor INTO id; KILL CONNECTION id; END LOOP kill_loop; END; CLOSE kill_cursor; --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. NOTES
For the --format option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g specifies the grid format. An error occurs if a prefix matches more than one valid value. EXAMPLES
For each example, assume that the root user on localhost has sufficient privileges to kill queries and connections. Kill all queries created by user mats that are younger than 1 minute: mysqlprocgrep --server=root@localhost --match-user=mats --age=-1m --kill-query Kill all connections that have been idle for more than 1 hour: mysqlprocgrep --server=root@localhost --match-command=sleep --age=1h --kill-connection COPYRIGHT
Copyright (c) 2010, 2012, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA AUTHOR
MySQL Utilities Team COPYRIGHT
2010, Oracle and/or its affiliates. All rights reserved. 1.0.3 May 09, 2012 MYSQLPROCGREP(1)
All times are GMT -4. The time now is 02:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy