01-25-2013
Vi Created empty file
Hi,
While creating a file by vi by mistake I created a file with empty name.
Please tell me how to delete it
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
What is the command to empty an already existing file.
please provide me.i used Touch cmd to empty the file.but it changing the time only. (4 Replies)
Discussion started by: laknar
4 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
How to we get to know when say a new log file is created on an Unix box.
I need to trigger a process(say a script) when the new log file is created.
But i need to know by some means or generate a trigger when a new file is created????
Something like when we receive a new mail we... (1 Reply)
Discussion started by: aixjadoo
1 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
I am checking for a empty input file to do some further action , but I am getting exit status 0 in both the cases , for empty and non empty file both.
The value of $? is coming 0 in if part also and else part too.
#!/bin/ksh
if ]; then
echo "data"
# exit 0
echo "$?"
else... (4 Replies)
Discussion started by: mavesum
4 Replies
4. AIX
Hi
i have aix 5.3 operating system, and i am trying to do ssh without passwd, when i tried to create a rsakey, it produces empty file as an output, how can solve that problem? why it is giving empty output file, i tried with different user, situation same,.i have restarted sshd server. .ssh... (2 Replies)
Discussion started by: nibiru78
2 Replies
5. Shell Programming and Scripting
I have a local linux machine in which the files are dumped by a remote ubuntu server. If the process in remote server has any problem then empty files are created in local machine. Is there any way using perl script to check if the empty files are being created and delete them and then run a shell... (2 Replies)
Discussion started by: hussa1n
2 Replies
6. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
When looking for corefiles, include any file with core in its name. (Some UNIX/Linux systems add the PID of the process that created the core to reduce the chances of overwriting an already existing core file that might be needed. The... (6 Replies)
Discussion started by: s3270226
6 Replies
7. UNIX for Dummies Questions & Answers
Hi!Can somebody tell me what command can I use to find who created a file,please? (6 Replies)
Discussion started by: teotrask
6 Replies
8. UNIX for Dummies Questions & Answers
Hi All
I use solaris 9 and just realised my opt volume has grown to 99%. How can I find out which file was created on the opt volume for it to have grown to 99%? Which command should I use since I can't go through each individual file to look at the date the files were created.
Regard (3 Replies)
Discussion started by: rahmantanko
3 Replies
9. Shell Programming and Scripting
Hi,
I have used expdp for datapump. The .dmp file is created by the "oracle" user.
my requirement is to make a zipped file of this .dmp file.
What i am trying to do is change the permissions of this .dmp file from 0640 to 0644 and then do a gzip and zip it. Is there any way i can change... (3 Replies)
Discussion started by: qwertyu
3 Replies
10. Shell Programming and Scripting
hi,
i have a script wrriten where there is a temporary files getting created:
echo "From:" ${usrname}@apps.mc.xerox.com>mail_txt
it was working from a long time but now there is a error creating while creating this temporary file. here is the error log for this:... (15 Replies)
Discussion started by: lovelysethii
15 Replies
PASSWD(5) File Formats Manual PASSWD(5)
NAME
passwd - password files
DESCRIPTION
Passwd files are files consisting of newline separated records, one per user, containing ten colon (``:'') separated fields. These fields
are as follows:
name user's login name
password user's encrypted password
uid user's id
gid user's login group id
class user's general classification (unused)
change password change time
expire account expiration time
gecos general information about the user
home_dir user's home directory
shell user's login shell
The name field is the login used to access the computer account, and the uid field is the number associated with it. They should both be
unique across the system (and often across a group of systems) since 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.
Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate
the fields in the user database.
The password field is the encrypted form of the password. If the password field is empty, no password will be required to gain access to
the machine. This is almost invariably a mistake. Because these files contain the encrypted user passwords, they should not be readable
by anyone without appropriate privileges.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning.
The class field is currently unused. In the near future it will be a key to a termcap(5) style database of user attributes.
The change field is the number in seconds, GMT, from the epoch, until the password for the account must be changed. This field may be left
empty to turn off the password aging feature.
The expire field is the number in seconds, GMT, from the epoch, until the account expires. This field may be left empty to turn off the
account aging feature.
The gecos field normally contains comma (``,'') separated subfields as follows:
name user's full name
office user's office number
wphone user's work phone number
hphone user's home phone number
This information is used by the finger(1) program.
The user's home directory is the full UNIX path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed.
SEE ALSO
chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8)
BUGS
User information should (and eventually will) be stored elsewhere.
7th Edition May 8, 1989 PASSWD(5)