05-15-2006
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
could probably help me with a unix problem.
Basicallyu, when the users try to connect to the server they get this messge:
No UTMP entry. you must exec "LOGIN" from the lowest level "sh"
They are connecting using a windows emulator called TINYTERM.
We cannot connect from the console either... (3 Replies)
Discussion started by: jernesto_diaz
3 Replies
2. SCO
We have made numerous requests to our system administrator to add new employees at login screen ( passwords not required ) to no avail.
I can login into root but not sure how to proceed from there.
We have a 10 yr. old version of SCO
Can anyone help?
I know very few unix commands okay... (1 Reply)
Discussion started by: houseostyle
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Is there is a good collection of Links to Unix Related stuff?
Regards,
Kriss (1 Reply)
Discussion started by: Kriss
1 Replies
4. Solaris
Hello World ~
HW : SUN Fire V240
OS : Solaris 8
Error message prompts 'rmclomv ... SC login failure ...' on terminal.
and
Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S)
The System is in normal operation, though
In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies
5. UNIX for Advanced & Expert Users
Hello,
I created a user in my AIX 5.3 system and i modified /etc/passwd file in and assigned this user the uid=0 like root user.
The problem is that when this user log into the system through putty it asks for root password instead of the user password.
As a result of this, if i reset the... (4 Replies)
Discussion started by: omonoiatis9
4 Replies
6. UNIX for Dummies Questions & Answers
Hello - Could anyone please explain what is login class in unix..? is it supported by Linux, AIX, HP-UX, Solaris?
Also how do we update this when a user is created? I looked into man pages for useradd/usermod and mkuser, but could not find any option to add/update login class for a user.
... (5 Replies)
Discussion started by: manju--
5 Replies
7. Shell Programming and Scripting
Hi Every body,
I would need a shell script program to login as different user and perform some copy commands in the script.
example: Supppose ora_toms is the active user
ora_toms should be able to run a script where user: ftptomsp pass: XXX should login through and run the commands
... (9 Replies)
Discussion started by: ujjwal27
9 Replies
8. AIX
I want to learn AIX. I would like to find someone who would be willing to give me a login to their AIX home lab server. My intent is to poke around and discover the similarities and differences of AIX compared to other *NIXs.
I am a UNIX admin so I can think of what some immediate concerns may... (1 Reply)
Discussion started by: perl_in_my_shel
1 Replies
9. Shell Programming and Scripting
now i have logged in username : ramesh in unix
Now i have to created script file to login into another user and have run a command inside that user and after executing the command i have to exit from that user.
Inside script, i have to login into su - ram along with password : haihow and have to... (4 Replies)
Discussion started by: rammm
4 Replies
10. Shell Programming and Scripting
Hi.
I inject my tracklogin.sh script in the profile of each user.
$ more .profile
./tracklogin.sh
# This is the default standard profile provided to a user.
MAIL=/usr/mail/${LOGNAME:?}
bash-3.2$ more tracklogin.sh
#!/bin/bash
tdate=$(date +"%d%m%y")
mkdir -p /tmp/root_log... (20 Replies)
Discussion started by: mohtashims
20 Replies
AND(8) Administrator's Tools AND(8)
NAME
and - auto nice daemon
SYNOPSIS
and [-htvsxf] [-i interval] [-c /path/to/and.conf] [-d /path/to/and.priorities]
VERSION
This manual page documents and version 1.2.2.
DESCRIPTION
The auto nice daemon activates itself in certain intervals and renices and even kills jobs according to their priority and CPU usage.
Renice levels and kill signals can be defined in terms of users, groups, and commands. Wildcards can be specified for any of these. In
addition, commands can be specified using POSIX regular expressions. To allow for network-wide configuration and priority files, a mecha-
nism for hostname-based evaluation is provided, again supporting regular expressions for specifying host names.
Jobs owned by root are left alone. Jobs are never increased in their priority.
Here are some real-world examples:
A certain user is notorious for wasting CPU with next-to-irrelevant jobs. One line is sufficient to renice all of his jobs to about 19.
This is a typical situation for a LART (Luser's Attitude Readjustment Tool) like and.
A CPU server is dedicated to a certain group, but others may also use it when it's idle. Just define default nice levels of e.g. 18 and a
lower nice level for the privileged group, say nice level 12.
A certain web browser who shall remain unnamed tends to go berserk once in a while. You can configure and to kill -9 it after e.g. 20 CPU
minutes.
COMMAND-LINE OPTIONS
-c /path/to/and.conf
Specifies the configuration file. If this flag is omitted, /etc/and.conf is used instead.
-d /path/to/and.priorities
Specifies the priority database file. If this flag is omitted, /etc/and.priorities is used instead.
-h Produces a short help text.
-i interval
Sets the interval between nice level checks. This flag overrides the interval specified in the configuration file, if any. The default
interval of 60 seconds is used if neither -i nor an interval directive in the configuration file is given.
-s Log to stdout. Without this switch, logging goes to syslog (normal operations) or ./debug.and (test mode). Useful for debugging config
files.
-t Run in test mode only, i.e. don't really renice or kill anything. In this mode, logging goes into ./debug.and instead of syslog.
-v Increase verbosity. For maximum verbosity, this flag can be specified multiple times. Be warned that this will blow up your log files,
so you should use it in test mode only.
-x Run in full operational mode, i.e. really renice or kill things. This is the default.
-f Foreground mode. Don't daemonize.
SIGNALS
On kill -HUP the auto nice daemon will reload its configuration file and priority database.
FILES
/etc/and.conf
General configuration file. Stores default nice level, default interval, the "time zones" and the database lookup affinity.
/etc/and.priorities
The priority database (in plain text). Contains the (user, group, command, nicelevels) tuples.
Both files have their own manual pages.
./debug.and
Contains logging and status information for debugging purposes. Used in test mode only.
SEE ALSO
and.conf(5), and.priorities(5), kill(1), regex(7), renice(8)
INTERNET
http://and.sourceforge.net/
AUTHOR
The auto nice daemon and this manual page were written by Patrick Schemitz <schemitz@users.sourceforge.net>
Unix 27 Mar 2005 AND(8)