10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am getting below error in fmadm output. This server is not in support, so can't reach them. Is it showing that motherboard is faulty and should be replaced ? It was rebooted a week back and then, there were no errors
# fmadm faulty
--------------- ------------------------------------ ... (1 Reply)
Discussion started by: solaris_1977
1 Replies
2. HP-UX
I recently picked up an HP9000 server running HPUX. I would like to replace the CRT terminal console with something I can use a flat panel monitor. Any suggestions would be greatly appreciated. (1 Reply)
Discussion started by: Stevebei
1 Replies
3. UNIX for Dummies Questions & Answers
my filename.txt looks like this:
2079951061790 SCK0000891539000000000000021600R
2079951061790 SCK0000901487000000000000028900R
2079951061790 SCK0000903092000000000000021300R
2079951074758 ... (9 Replies)
Discussion started by: tjmannonline
9 Replies
4. Shell Programming and Scripting
Hi
pls help me for below;
i have a file .content is :
===================
uid,pcsPricingPlan,refPcsQosProfName
821910002022,smartlimit,SGSNQOS1
i have to replace the value of uid and pricingplan by a unix script.
may be the value would be next line or any where in the file.
pls... (9 Replies)
Discussion started by: Aditya.Gurgaon
9 Replies
5. Shell Programming and Scripting
Hi,
i have a file with lines,
file.txt
-------
test is fun
testing is better
I need to replace 'test' to 'develop' and i used,
a=test
b=develop
sed "s,$a,$b,g" -------- but i see the word 'testing' is also replaced. Need some solution. Is there any way i could replace only 'test' ? (4 Replies)
Discussion started by: giri_luck
4 Replies
6. Shell Programming and Scripting
This seems like it should be an easy problem, but I'm a noob and I can't figure it out. I'm trying to use sed, but would be happy to use anything that does the job.
I am trying to trim off a fixed number of unknown characters from 2 different : delimited fields while keeping the intervening... (4 Replies)
Discussion started by: helix_w
4 Replies
7. Shell Programming and Scripting
Hi All,
I have below file which has data in below format.
#$ | AB_100
| AB_300
()| AB_4
@*(% | AB-789
i want o/p as below format.
| AB_100
| AB_300
| AB_4
| AB-789
So here there is no standard format.
How we can achieve the same in unix ?
Regards, (3 Replies)
Discussion started by: gander_ss
3 Replies
8. UNIX for Advanced & Expert Users
I've been tasked with converting our software from strictly an IPv4 environment to handling both IPv4 and IPv6. I'm very nearly done and everything seems to be progressing just fine. There's just one thing that's been nagging me for a while now, so I thought I'd enquire about this.
I've read... (1 Reply)
Discussion started by: sszd
1 Replies
9. Shell Programming and Scripting
Hi
Can anyone provide me the replacement of sed with xargs perl syntax for the below
sed -e :a -e '/;$/!N;s/\n//; ta' -e 's/;$//'
This should be without looping has to take minimal time for search (0 Replies)
Discussion started by: dbsurf
0 Replies
10. UNIX for Dummies Questions & Answers
I have two files:
file1:
somedata
<html>
<head>
This is sample statement
......
......
</head>
</html>
somedata
file2:
olga 81 91 B A
rene 82 92 B A
zack 83 93
Expextd Result: (2 Replies)
Discussion started by: rajx
2 Replies
CHPASS(1) BSD General Commands Manual CHPASS(1)
NAME
chpass, chfn, chsh, -- add or change user database information
SYNOPSIS
chpass [-a list] [-p encpass] [-e expiretime] [-s newshell] [user]
DESCRIPTION
The chpass utility allows editing of the user database information associated with user or, by default, the current user.
The chfn, and chsh utilities behave identically to chpass. (There is only one program.)
The information is formatted and supplied to an editor for changes.
Only the information that the user is allowed to change is displayed.
The options are as follows:
-a The super-user is allowed to directly supply a user database entry, in the format specified by passwd(5), as an argument. This argu-
ment must be a colon (``:'') separated list of all the user database fields, although they may be empty. [Note that this only
changes the user database, master.passwd.]
-p The super-user is allowed to directly supply an encrypted password field, in the format used by crypt(3), as an argument. [See the
discussion in getpwent(3) about types of passwords; this option may not be appropriate.]
-e expiretime
Change the account expire time. This option is used to set the expire time from a script as if it was done in the interactive edi-
tor.
-s newshell
Attempt to change the user's shell to newshell.
Possible display items are as follows:
Login: user's login name
Password: user's encrypted password [do not use this to change a password; use passwd(1) instead]
Uid: user's login
Gid: user's login group
Class: user's general classification
Change: password change time
Expire: account expiration time
Full Name: user's real name (*)
Home Directory: user's home directory
Shell: user's login shell
NOTE(*) - Historically, the so-call "GECOS" field in the user database entry contain the full name plus other information.
Only the full name is currently supported.
The login field is the user name used to access the computer account.
The password field contains the encrypted form of the user's password. Do not use this to change a password; use passwd(1) instead.
The uid field is the number associated with the login field. Both of these fields should be unique across the system (and often across a
group of systems) as they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so. Rou-
tines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The group field is the group that the user will be placed in at login. Since BSD supports multiple groups (see groups(1)) this field cur-
rently has little special meaning. This field may be filled in with either a number or a group name (see group(5)).
The class field references class descriptions in /etc/login.conf and is typically used to initialize the user's system resource limits when
they login.
The change field is the date by which the password must be changed.
The expire field is the date on which the account expires.
Both the change and expire fields should be entered in the form ``month day year'' where month is the month name (the first three characters
are sufficient), day is the day of the month, and year is the year.
The full name field contains the full name of the user.
The user's home directory is the full UNIX path name where the user will be placed at login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell, /bin/sh, is assumed. When
altering a login shell, and not the super-user, the user may not change from a non-standard shell or to a non-standard shell. Non-standard
is defined as a shell not found in /etc/shells.
Once the information has been verified, chpass uses pwd_mkdb(8) to update the user database.
LOOKUPD AND DIRECTORY SERVICE AWARENESS
User database entries (among other things) are under the control of lookupd(8) and may be physically located in many different places,
including local and remote netinfo(5) databases, directory service agents such as LDAP servers and flat file databases such as master.passwd.
This version of chpass is currently limited to changing user database entries in the flat file and local netinfo databases.
ENVIRONMENT
The vi(1) editor will be used unless the environment variable EDITOR is set to an alternate editor. When the editor terminates, the informa-
tion is re-read and used to update the user database itself. Only the user, or the super-user, may edit the information associated with the
user.
See pwd_mkdb(8) for an explanation of the impact of setting the PW_SCAN_BIG_IDS environment variable.
FILES
/etc/master.passwd the user database
/etc/passwd a Version 7 format password file
/etc/chpass.XXXXXX temporary copy of the password file
/etc/shells the list of approved shells
SEE ALSO
finger(1), login(1), passwd(1), getusershell(3), login.conf(5), passwd(5), pwd_mkdb(8), vipw(8)
and Robert Morris and Ken Thompson, UNIX Password security.
BUGS
User information should (and eventually will) be stored elsewhere.
HISTORY
The chpass utility appeared in 4.3BSD-Reno.
BSD
December 30, 1993 BSD