08-15-2011
Is this the default that the rpm installed for you? or have you changed some setting in there?
If you did make any changes, I would like to try starting vsftpd with just the default conf file in place. You may have to yum erase vsftp and yum install vsftp to get the defaults again or if created a backup before making changes, then you can copy the default back.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Backup Exec Agent won't start....
Question: Has anyone had any previous experience working with Backup exec for Unix? I'm running SCO Openserver 5.0.5 and Backup Exec agent Version 5.01 Revision 5.032 Basically, these are the commands I'm issueing and here is the output.
# cd etc
# cd... (1 Reply)
Discussion started by: PatMcCoy
1 Replies
2. Solaris
Hi
Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies
3. UNIX for Dummies Questions & Answers
After I log ino the machine, a window pops up indicating that I should check that the HOSTNAME is the same in these three files
/etc//rc.configd/netconf
/etc/hosts
/var/adm/inetd.sec
How do I change the hostname in these files?
Thanks,
Mike h (1 Reply)
Discussion started by: hutchin
1 Replies
4. SuSE
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Discussion started by: dave521
5 Replies
5. Solaris
Hi.
I got this message in our sun station and it stuck
Setting default IPv4 interface for multicast: add net 224.0/4: gateway pecsun22
but i can still telenet the station...
who could i fix this..
appreciate your help (7 Replies)
Discussion started by: eykyn17
7 Replies
6. Red Hat
im running rh 9 on my vmware, i tryed changing the graphics card mode
to resize the desktop, after restarting i get a message X Server cannot start.
then it takes me to the consol screen to log on, "im new to using linux as of last night"
It would be helpfull if anyone can help me resolve... (4 Replies)
Discussion started by: aoteg
4 Replies
7. Solaris
if anyone can help me here I will be in debt eternaly. I'm in a spot here fearing for my job.
I tried to install a new scsi array on our E5500. I powered it down correctly, removed the terminator, connected the array and powered it on. It was taking so long to come up I freaked out and powered... (3 Replies)
Discussion started by: NewSolarisAdmin
3 Replies
8. UNIX for Dummies Questions & Answers
on my AIX 6.1 CDE's ToolTalk server won't start. It says:
dtsession: Unable to exec /usr/dt/install/oldrules/dtrmrules.driver.
A file or directory in the path name does not exist.
How can I fix this? (0 Replies)
Discussion started by: rein
0 Replies
9. AIX
Hi,
My NFS does not work till I start HACMP. The NFS service is indeed started when server starts. But it is not in active state, when I use lssrc to check NFS services' status I find they are all in inoperative status. But after I start HACMP (smitty clstart), all NFS services become active... (4 Replies)
Discussion started by: qiulang
4 Replies
10. Fedora
Okay, I'm fairly green at Fedora, but it has worked like a gem until now. On startup I get a screen that says this:
Booting 'Fedora (3.6.11-4.fc16.x86_64)'
Loading Fedora (3.611-4.fc16.x86_64)
Loading initial ramdisk ....
_Fedora-16-x86_6: Unexpected inconsistency; run fsck manually.
... (6 Replies)
Discussion started by: Anchorsteamer
6 Replies
LEARN ABOUT CENTOS
yum-versionlock.conf
YUM-VERSIONLOCK.CONF(5) File Formats YUM-VERSIONLOCK.CONF(5)
NAME
yum-versionlock.conf(5)
SYNOPSIS
yum-versionlock.conf(5) is the configuration file for yum-versionlock(1) Yum plugin for excluding packages that aren't listed in the ver-
sionlock file. The plugin will walk each line of the versionlock file, parse out the name and version of the package. It will then exclude
any package by that name that doesn't match one of the versions listed within the file (or, optionally, any obsoleter of that package).
This is basically the same as doing an exclude for the package name itself (as you cannot exclude installed packages), but yum will still
see the versions you have installed/versionlocked as available so that "yum reinstall" will still work, etc. It can also work in the oppo-
site way, like a fast exclude, by prefixing a '!' character to the version.
FILES
/etc/yum/pluginconf.d/versionlock.conf
FILE FORMAT
yum-versionlock.conf(5) utilizes configuration options in the form of
OPTION=VALUE
OPTION
follow_obsoletes
This option is a boolean flag which specifies if the versionlock plugin should look at all the obsoletes, and see if any of the
packages specified have an obsoleter. If an obsoleter is found then all versions of that package will be excluded. This option is
off by default, as yum-versionlock(1) will take some time to do the obsoletes processing, and for non-rename obsoletes any issues
you had which kept you at a specific version of a package should be different with another package.
OPTION
locklist
This option is a string with points to the file which will have the versionlock information in it. Note that the file has to exist
(or the versionlock plugin will make yum exit). However it can be empty.
AUTHOR
Chitlesh Goorah <chitlesh@fedoraproject.org>
James Antill <james@fedoraproject.org>
SEE ALSO
yum-versionlock(1)
27 July 2008 YUM-VERSIONLOCK.CONF(5)