What will happen if you recompile and install applications in Linux?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What will happen if you recompile and install applications in Linux?
Know it's a newbie questions but I am not sure of the answer, also I'm away from my VM workstation so I can not test this.
I'm working on a system, looks like xinetd is having some start up issues. I could reinstall it using yum but looking at the /etc/xinetd.d folder, there's already a few config files there for other applications.
So if I run a new version xinetd I just download, ./configure, make, make install, will that overwrite all of the config files already in /etc/xinetd.d?
I searched but didn't find much about this, I assume it would leave the current files in the same place.
Know it's a newbie questions but I am not sure of the answer, also I'm away from my VM workstation so I can not test this.
I'm working on a system, looks like xinetd is having some start up issues. I could reinstall it using yum but looking at the /etc/xinetd.d folder, there's already a few config files there for other applications.
So if I run a new version xinetd I just download, ./configure, make, make install, will that overwrite all of the config files already in /etc/xinetd.d?
I searched but didn't find much about this, I assume it would leave the current files in the same place.
Thanks,
Rob
Your distro says Ubuntu, but you're using yum?
Anyway ... I'd recommend against that - see whether yum knows
about an updated/bug-fixed version (if that is indeed the
problem). And as bret said: what errors are you seeing in
the first place?
I did a install of nrpe, and part of the install requires xinetd. In other servers it was not installed so I installed it either from yum or apt-get but on this server it's already in place.
While I checked nrpe by "netstat -at | grep nrpe" nothing came back.
Checking the services by "service --status-all | grep xinetd" comes back with.
[root@ns2 etc]# service --status-all | grep xinetd
/etc/init.d/avahi-daemon: line 21: [: =: unary operator expected
/etc/init.d/avahi-dnsconfd: line 21: [: =: unary operator expected
capi not installed - No such file or directory (2)
/etc/init.d/conman: line 16: [: =: unary operator expected
/etc/init.d/netplugd: line 21: [: =: unary operator expected
/etc/init.d/ntpd: line 19: [: =: unary operator expected
/etc/init.d/rdisc: line 25: [: =: unary operator expected
/etc/init.d/rwhod: line 16: [: =: unary operator expected
/etc/init.d/smb: line 32: [: =: unary operator expected
/etc/init.d/squid: line 25: [: =: unary operator expected
squid: ERROR: No running copy
/etc/init.d/vncserver: line 14: [: =: unary operator expected
/etc/init.d/vsftpd: line 19: [: =: unary operator expected
/etc/init.d/winbind: line 30: [: =: unary operator expected
/etc/init.d/ypbind: line 28: [: =: unary operator expected
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
isnt ubuntu moving away from xinetd to upstart? perhaps you should look at upstart and remove the offending entries from your xinetd config as perhaps they have been migrated to upstart instead
I should have noted that this is Redhat version 4 not Ubuntu. I followed the same steps on Ubuntu with no issues but also xinetd is not used either since I installed it fresh.
I did search the files that were referenced in the error message and here's the line number 21 in the first two.
[ ${NETWORKING} = "no" ] && exit 0
The servers are our DNS servers so I'm hesitant to make any changes until I find out what is causing this.
I did a install of nrpe, and part of the install requires xinetd. In other servers it was not installed so I installed it either from yum or apt-get but on this server it's already in place.
While I checked nrpe by "netstat -at | grep nrpe" nothing came back.
Checking the services by "service --status-all | grep xinetd" comes back with.
[root@ns2 etc]# service --status-all | grep xinetd
/etc/init.d/avahi-daemon: line 21: [: =: unary operator expected
/etc/init.d/avahi-dnsconfd: line 21: [: =: unary operator expected
capi not installed - No such file or directory (2)
/etc/init.d/conman: line 16: [: =: unary operator expected
/etc/init.d/netplugd: line 21: [: =: unary operator expected
/etc/init.d/ntpd: line 19: [: =: unary operator expected
/etc/init.d/rdisc: line 25: [: =: unary operator expected
/etc/init.d/rwhod: line 16: [: =: unary operator expected
/etc/init.d/smb: line 32: [: =: unary operator expected
/etc/init.d/squid: line 25: [: =: unary operator expected
squid: ERROR: No running copy
/etc/init.d/vncserver: line 14: [: =: unary operator expected
/etc/init.d/vsftpd: line 19: [: =: unary operator expected
/etc/init.d/winbind: line 30: [: =: unary operator expected
/etc/init.d/ypbind: line 28: [: =: unary operator expected
You'll probably notice that none of those lines have
got anything to do with xinetd. They're error messages
that service --status-all is outputting, and that grep
isn't processing since they're on stderr, not stdout.
So chances are that service itself is the culprit. What
do you get w/o the grep tacked on?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.