9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All,
I have a text file containing output from a command that contains lots of escape/control characters that when viewed using vi or view, looks like jibberish. But when viewed using the cat command the output is formatted properly.
Is there any way to take the output from the cat... (7 Replies)
Discussion started by: mrm5102
7 Replies
2. Shell Programming and Scripting
How to show the type of my terminal?
Thanks in advance! (1 Reply)
Discussion started by: Henryyy
1 Replies
3. Red Hat
Hi,
I'm using CentOS 5.5. I connected serial terminal using "cu". The command I had given was "cu -l /dev/ttyUSB0 -s 115200". It connects I'm seeing the target boards boot-up messages and log in screen. But I couldn't type anything on "cu" terminal window.
Any help is highly appreciated.
... (1 Reply)
Discussion started by: suryaemlinux
1 Replies
4. UNIX for Advanced & Expert Users
I'm not sure if this is the right place to post this, but here it is. We have a nightly process that runs on an HP-UX box to stop our application and backend database servers, unmount their SAN hosted file systems, and then snapshot the SAN LUNs for backup and refresh of data on "report" and... (1 Reply)
Discussion started by: deckard
1 Replies
5. Shell Programming and Scripting
Hi,
Can anyone help me parse the code bellow. I have a file with several lines. I ant to put an 'X' on the lines that ONLY have an '=' in them ignoring comma's, spaces etc..
So:
/*
,
systems.menuLabel.new=New
systems.menuLabel.new.mnemonic=N
*/
Would look like:
/*
,
... (9 Replies)
Discussion started by: jascas
9 Replies
6. Solaris
The answer to my problem might be to get a Sun console but I thought I would run it by the experts here first. I have been trying to install Sun Solaris on a SunFire V445 using an HPconsole (just happens to be all I have at my disposal at the moment) and no network connection yet. When I am... (1 Reply)
Discussion started by: scotbuff
1 Replies
7. Shell Programming and Scripting
I'd like to make a script that I can execute every time I sign on to my linux box that keeps track of the time and allows to me to add a remark to a file. So basically once I log in, I run the script, and it outputs the date and time to a text file (log.txt). But that isn't my problem.
I need... (1 Reply)
Discussion started by: Glider
1 Replies
8. SCO
Dear all,
I need to change the terminal type to vt100 for all the users pls guide me for this (1 Reply)
Discussion started by: asahcl
1 Replies
9. UNIX for Advanced & Expert Users
hey,
I use cygwin to connect to AIX 5.2 but when I open vi I get an error saying:
ex: 0602-108 cygwin is not a recognized terminal type
how can I fix that? I thought cygwin was tty vt100? (1 Reply)
Discussion started by: rein
1 Replies
d_passwd(4) File Formats d_passwd(4)
NAME
d_passwd - dial-up password file
SYNOPSIS
/etc/d_passwd
DESCRIPTION
A dial-up password is an additional password required of users who access the computer through a modem or dial-up port. The correct pass-
word must be entered before the user is granted access to the computer.
d_passwd is an ASCII file which contains a list of executable programs (typically shells) that require a dial-up password and the associ-
ated encrypted passwords. When a user attempts to log in on any of the ports listed in the dialups file (see dialups(4)), the login program
looks at the user's login entry stored in the passwd file (see passwd(4)), and compares the login shell field to the entries in d_passwd.
These entries determine whether the user will be required to supply a dial-up password.
Each entry in d_passwd is a single line of the form:
login-shell:password:
where
login-shell The name of the login program that will require an additional dial-up password.
password An encrypted password. Users accessing the computer through a dial-up port or modem using login-shell will be required to
enter this password before gaining access to the computer.
d_passwd should be owned by the root user and the root group. The file should have read and write permissions for the owner (root) only.
If the user's login program in the passwd file is not found in d_passwd or if the login shell field in passwd is empty, the user must sup-
ply the default password. The default password is the entry for /usr/bin/sh. If d_passwd has no entry for /usr/bin/sh, then those users
whose login shell field in passwd is empty or does not match any entry in d_passwd will not be prompted for a dial-up password.
Dial-up logins are disabled if d_passwd has only the following entry:
/usr/bin/sh:*:
EXAMPLES
Example 1: Sample d_passwd file.
Here is a sample d_passwd file:
/usr/lib/uucp/uucico:q.mJzTnu8icF0:
/usr/bin/csh:6k/7KCFRPNVXg:
/usr/bin/ksh:9df/FDf.4jkRt:
/usr/bin/sh:41FuGVzGcDJlw:
Generating An Encrypted Password
The passwd (see passwd(1)) utility can be used to generate the encrypted password for each login program. passwd generates encrypted pass-
words for users and places the password in the shadow (see shadow(4)) file. Passwords for the d_passwd file will need to be generated by
first adding a temporary user id using useradd (see useradd(1M)), and then using passwd(1) to generate the desired password in the shadow
file. Once the encrypted version of the password has been created, it can be copied to the d_passwd file.
For example:
1.
Type useradd tempuser and press Return. This creates a user named tempuser.
2. Type passwd tempuser and press Return. This creates an encrypted password for tempuser and places it in the shadow file.
3. Find the entry for tempuser in the shadow file and copy the encrypted password to the desired entry in the d_passwd file.
4. Type userdel tempuser and press Return to delete tempuser.
These steps must be executed as the root user.
FILES
/etc/d_passwd dial-up password file
/etc/dialups list of dial-up ports requiring dial-up passwords
/etc/passwd password file
/etc/shadow shadow password file
SEE ALSO
passwd(1), useradd(1M), dialups(4), passwd(4), shadow(4)
WARNINGS
When creating a new dial-up password, be sure to remain logged in on at least one terminal while testing the new password. This ensures
that there is an available terminal from which you can correct any mistakes that were made when the new password was added.
SunOS 5.10 2 Sep 2004 d_passwd(4)