03-08-2011
You might throw a truss on the daemon so you can see what system error occurs.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am a Linux / Unix newbie c programmer.
I have a c/c++ daemon server that will receive authentication (userid / password) from a windows client.
All I want to do is authenticate the user via PAM API - i.e. user must exist on the Unix / Linux system + password must be validated.
... (1 Reply)
Discussion started by: vineshp
1 Replies
2. UNIX for Advanced & Expert Users
I have a linux machine which authenticate users to ldap, this is working fine. But I would like to limit users that logon to the machines to just the system admins.
The machines hosts different web sites which users accessed from there home directory like http://foo.mdx.ac.uk/~username
At the... (0 Replies)
Discussion started by: hassan1
0 Replies
3. Solaris
HI,
There is a user having problem when he try to login to solaris box, it works after few tried. What may be the problem?
PAM authentication
Password:
PAM authentication
Password:
PAM authentication
New Password: (1 Reply)
Discussion started by: mokkan
1 Replies
4. Solaris
Hello Group,
I'm facing Problem with the configuration of "***pam_radius_auth.so.1***" module to be integrated with Freeradius and Funk Steel Belted Radius. Both this radius servers are able to make "Access-Accept" packet. But the SSH or Telnet client is not able to login to the system with the... (0 Replies)
Discussion started by: ImpeccableCode
0 Replies
5. UNIX for Advanced & Expert Users
My PAM module seems to work right but it fails in authentication. Althought it can't authenticate, the session module works and the software who uses it executes well.
For example, when I login through "gdm" using pam to authenticate against an ldap server
/var/log/auth.log shows
Any... (1 Reply)
Discussion started by: capibolso
1 Replies
6. UNIX for Dummies Questions & Answers
Greetings!
I just managed to install Solaris 10 on a Sparc based machine. However, there might be a problem with the way ssh is configured.
I CAN ssh from the machine into another on the network (same subnet, as root), but then the newly installed machine CANNOT seem to accept incoming ssh... (2 Replies)
Discussion started by: agummad
2 Replies
7. Red Hat
Hi,
I've configured two linux boxes to authenticate against Windows Active Directory using Kerberos while retrieving authorization data (uids, gids ,,,)from NIS.
The problem I ran into with my PAM configuration is that all authentication attempts succeed in order.i.e. if someone tried his... (0 Replies)
Discussion started by: geek.ksa
0 Replies
8. SCO
Hi all.
I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
Discussion started by: silk600
0 Replies
9. UNIX for Advanced & Expert Users
I have applied pam authentication for local users as highlighted in below file.
# cat /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so... (0 Replies)
Discussion started by: pinga123
0 Replies
10. SuSE
Hello all,
I recently updated PAM policy files (pam_authz.policy) on HP-UX Servers with AD groups involving allowing and denying the certain groups..
Could anyone tell me what is the equivalent mechanism in SLES(Linux)? Is it possible to allow/deny AD group access with the SLES LDAP... (0 Replies)
Discussion started by: lcclaj0
0 Replies
voliod(8) System Manager's Manual voliod(8)
NAME
voliod - Start, stop, and report on Logical Storage Manager kernel daemons
SYNOPSIS
/sbin/voliod
/sbin/voliod [-f] set count
OPTIONS
The following option is used by voliod: Force the kill of the last I/O daemon. Without this option, the I/O daemons can only be reduced to
one.
DESCRIPTION
The voliod utility starts, stops, or reports on Logical Storage Manager I/O daemons. An I/O daemon is a process that provides a process
context for processing any work that needs to be done to process Logical Storage Manager I/O.
When invoked with no arguments, voliod prints the current number of volume I/O daemons on the standard output.
When invoked with the set keyword, the number of daemons specified by count will be created. If more volume I/O daemons exist than are
specified by count, then the excess processes will be terminated. If more than the maximum number are created (currently 64), the requested
number will be silently truncated to that maximum.
The number of daemons to create for general I/O handling depends on system load and usage. One daemon for each CPU on the system is gener-
ally adequate, unless volume recovery seems unusually slow.
Each I/O daemon starts in the background and creates an asynchronously-running kernel thread and becomes a volume I/O daemon. The voliod
utility does not wait for these threads to complete.
NOTES
LSM automatically sets the number of I/O daemons when the system starts, so it is usually not necessary to set or change the number of I/O
daemons with this command.
LSM I/O daemons cannot be killed directly through the use of signals.
The number of Logical Storage Manager I/O daemons currently running can only be determined by running voliod; I/O daemons do not appear in
the list of processes produced by the ps(1) command.
EXIT CODES
The voliod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O error occurs within a spawned
I/O daemon thread, then the I/O is not reflected in the exit status for voliod. Otherwise, voliod returns a nonzero exit status on errors.
Usage errors result in an exit status of 1 and a usage message. If the requested number of daemons cannot be created, then the exit status
is 2, and the number of daemons that were successfully started is reported. If any other error occurs, the exit status is 3.
FILES
The device used to report on and start volume I/O daemon kernel threads.
SEE ALSO
fork(2), volintro(8), vold(8), voldctl(8) ,pthread(8)
voliod(8)