02-02-2009
On my HP-UX servers I have an "*" and on my RedHat Linux it has "x". I dont know about AIX and Solaris.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm tasked to change a user's password on multiple Linux systems (RH v3). I though copying the encrypted password from one Linux /etc/shadow file to another would work but I was wrong.
The long term solution is to establish an openLDAP Directory service, but for now I'm stuck with a manual... (1 Reply)
Discussion started by: benq70
1 Replies
2. Linux
We are currently using a script to copy the same encrypted password between our HP-UX and Solaris servers editing the trusted and shadow files directly. The encrypted password is only 13 characters long on both servers and decrypts the same way. Is there a way to copy this same string to Linux... (5 Replies)
Discussion started by: keelba
5 Replies
3. Solaris
i wonder if there is a tool to read the /etc/passwd or /etc/shadow files in order to reset user accounts to the same one.
By moving (restore) all filessytem and data to another same Sun box, none of the users are able to logon to the new box which i didn't change nothing. But if i reset the user... (1 Reply)
Discussion started by: lamoul
1 Replies
4. UNIX for Advanced & Expert Users
Hi
I wonder whether is possible to generate enrypted passwd for some user and paste it into /etc/shadow file ?
What kind of encryption is used in /etc/shadow file ?
ths for help. (1 Reply)
Discussion started by: presul
1 Replies
5. Solaris
Hi Folks,
I have Solaris 10, latest release.
We have passwd aging set in /etc/defalut/passwd.
I have an account that passwd should never expire. Acheived by emptying associated users shadow file entries for passwd aging.
When I reset the users passwd using passwd command, it re enables... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
6. Solaris
Hi , can anyone explain me the difference between /etc/shadow and /etc/default/passwd . As per my knowledge both the files are used for password aging and control parameters. (2 Replies)
Discussion started by: rogerben
2 Replies
7. UNIX for Advanced & Expert Users
hi, all
I just started on new box where I have to diff passwd working perfectly on the very same account/user. I see that shadow was added recently (I'm not a root in there), I see 'x' in passwd. Not sure how it should work, should I change old passwd for one defined in shadow? Or it's fine to... (20 Replies)
Discussion started by: trento17
20 Replies
8. AIX
Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords? (1 Reply)
Discussion started by: Anne Neville
1 Replies
9. Shell Programming and Scripting
Hello friends,
We have encrypted password strings for all of our users (each user has different password).
After creating users in Linux, we replace encrypted passwords manually on /etc/shadow so that their passwords directly work. Instead we want to do it using scripting.
I tried with sed... (2 Replies)
Discussion started by: prvnrk
2 Replies
10. UNIX for Dummies Questions & Answers
i have an application that uses the encrypted password that's in the /etc/shadow file.
i copied the line for the particular username i was interested it in from shadow file and i pasted it into the password file of the application. the application is nagios.
this application allowed that... (5 Replies)
Discussion started by: SkySmart
5 Replies
GSIGNAL(3) Linux Programmer's Manual GSIGNAL(3)
NAME
gsignal, ssignal - software signal facility
SYNOPSIS
#include <signal.h>
typedef void (*sighandler_t)(int);
int gsignal(intsignum);
sighandler_t ssignal(int signum, sighandler_t action);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
gsignal(), ssignal(): _SVID_SOURCE
DESCRIPTION
Don't use these functions under Linux. Due to a historical mistake, under Linux these functions are aliases for raise(3) and signal(2),
respectively.
Elsewhere, on System V-like systems, these functions implement software signaling, entirely independent of the classical signal(2) and
kill(2) functions. The function ssignal() defines the action to take when the software signal with number signum is raised using the func-
tion gsignal(), and returns the previous such action or SIG_DFL. The function gsignal() does the following: if no action (or the action
SIG_DFL) was specified for signum, then it does nothing and returns 0. If the action SIG_IGN was specified for signum, then it does noth-
ing and returns 1. Otherwise, it resets the action to SIG_DFL and calls the action function with argument signum, and returns the value
returned by that function. The range of possible values signum varies (often 1-15 or 1-17).
CONFORMING TO
These functions are available under AIX, DG/UX, HP-UX, SCO, Solaris, Tru64. They are called obsolete under most of these systems, and are
broken under Linux libc and glibc. Some systems also have gsignal_r() and ssignal_r().
SEE ALSO
kill(2), signal(2), raise(3)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2007-07-26 GSIGNAL(3)