Re: [CentOS] octave
John wrote: This one is for EPEL 5 on there site. http://rpm.pbone.net/index.php3/stat/4/idpl/8177721/com/hdf5-1.6.7-1.el5.i38 6.rpm.html I installed the hdf5 package off EPEL (via yum install hdf5) and my yum install octave still fails with the same error. Error: Missing Dependency: libhdf5.so.0 is needed by package octave when I look at that hdf5 package, I see... # rpm -ql hdf5 /usr/bin/gif2h5 /usr/bin/h52gif /usr/bin/h52gifgentst /usr/bin/h5cc /usr/bin/h5copy /usr/bin/h5debug /usr/bin/h5diff /usr/bin/h5dump /usr/bin/h5import /usr/bin/h5jam /usr/bin/h5ls /usr/bin/h5mkgrp /usr/bin/h5redeploy /usr/bin/h5repack /usr/bin/h5repart /usr/bin/h5stat /usr/bin/h5unjam /usr/lib/libhdf5.settings /usr/lib/libhdf5.so.5 /usr/lib/libhdf5.so.5.0.0 /usr/lib/libhdf5_hl.so.0 /usr/lib/libhdf5_hl.so.0.0.0 /usr/share/doc/hdf5-1.8.0 /usr/share/doc/hdf5-1.8.0/COPYING /usr/share/doc/hdf5-1.8.0/README.txt libhdf5.so.5 and .5.0.0 and _hl.so.0 != what octave is looking for. I know EPEL isn't a CentOS project, IIRC, its a Fedora/RH projecct but this isn't looking good. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DHCP static hosts and subnet configuration
Dear John, >> Subnet A (192.168.2.x) <-> DHCP Server with 2 NICs <-> Subnet B (10.1.0.0) >> >> Clients on Subnet A should get a static IP from the host declaration. >> Clients on Subnet B should obtain dynamic IP addresses from a range. >> The two subnets are not physically connected but a CLIENT should be >> able to connect to Subnet A or to Subnet B as well. > This is what is confusing. If there *NOT* Physically Connected you will > never CONNECT to them. In this setup Subnet A is a private network and Subnet B is a network for public Wifi access. If one got a notebook and his/her mac-address is listed in Subnet A declaration he/she should be able to obtain an IP. In some situations this machine may just want to access to public wifi so he/she should also be able to connect to Subnet B as well. ATM, the client will only get an IP address if there is a static host declaration for it in both networks. Otherwise it would just be able to connect to Subnet A and will never receive an IP from the dynamic range of Subnet B. In the near future Subnet A will be migrated to a Class A network, so 'subnetting' may be possible, but I don't think that this will change the situation. I also wonder if it's really necessary to run two instances of DHCP with separate config files as dhcpd3 is able to detect the Subnets on which it may deploy leases, depending on the NIC configuration. Best Regards Marcus ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] -bash: /bin/grep: cannot execute binary file
Hi all,I have problem on CentOS 5.2 while everything is working great,suddenly i have this error when i login my server, sudo su - -bash: /bin/egrep: cannot execute binary file -bash: /bin/egrep: cannot execute binary file -bash: /bin/egrep: cannot execute binary file -bash: /bin/hostname: cannot execute binary file -bash: /bin/grep: cannot execute binary file -bash: /bin/grep: cannot execute binary file -bash: /bin/grep: cannot execute binary file -bash: /bin/grep: cannot execute binary file [EMAIL PROTECTED] ~]# and when i try use vi editor,i have same error like above -bash: /bin/vi: cannot execute binary file What is problem do you think ? i searched this problem on google but did not found any reasonable answer. Thanks all for all helps. -- Iyi calismalar.Basarilar... Semih Gokalp Istanbul/Turkiye ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: ls and rm: "argument list too long"
On Fri, 2008-10-17 at 23:52 -0500, Les Mikesell wrote:
> Robert Nichols wrote:
> >
> >> These shouldn't make any difference. The limit is on the size of the
> >> expanded shell command line.
> >
> > Really?
> >
> > $ M=0; N=0; for W in `find /usr -xdev 2>/dev/null`; do M=$(($M+1));
> > N=$(($N+${#W}+1)); done; echo $M $N
> > 156304 7677373
> >
> > vs.
> >
> > $ /bin/echo `find /usr -xdev 2>/dev/null`
> > bash: /bin/echo: Argument list too long
> >
> > For the first case, the shell never tries to pass the list as command
> > arguments.
> > It builds the list internally, limited only by memory size, and
> > processes the
> > words one by one.
>
> Is that peculiar to bash? I thought the `command` construct was
> expanded by shells into the command line before being evaluated.
IIRC, none of the above make a "command line". Everything but the
`find /usr -xdev 2>/dev/null`
is a bash "internal command". IIRC, what should happen here is a new
instance of bash is spawned as part of a pipeline that sends the output
of the find (which is "exec'd" by that new instance of bash, the child)
into the parent. The parent reads the input from the pipe and can do
whatever it wants, in this case build an array. It then uses the array
as data to the loop.
The "command line" is never constructed with the long list. It is only
passed to the child (the new instance of bash that is part of the
pipeline). That instance receives an argument count and an array of
pointers to the arguments. In "C" parlance it looks something like this.
main(argc, *argv[]) /* could be **argv instead */
{
/* stuff to do */
.
.
.
}
The "*argv[]" pointers point to the parts of the "command line",
find /usr -xdev
The child execs find, passing the "/usr" and "-xdev" as arguments to
find (which has a similar "main" construct), another "command line". The
I/O redirection was already done by the parent, so the child need not
even know that "stdout" is a pipe.
The longest command line in this case is "find /usr -xdev', 15
characters. Find "sees" only 10 characters.
I hope I've remembered correctly, that this is not FUD, and that it
helps someone.
>
--
Bill
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] octave
I installed the hdf5 package off EPEL (via yum install hdf5) and my yum install octave still fails with the same error. Error: Missing Dependency: libhdf5.so.0 is needed by package octave when I look at that hdf5 package, I see... # rpm -ql hdf5 /usr/bin/gif2h5 /usr/bin/h52gif /usr/bin/h52gifgentst /usr/bin/h5cc /usr/bin/h5copy /usr/bin/h5debug /usr/bin/h5diff /usr/bin/h5dump /usr/bin/h5import /usr/bin/h5jam /usr/bin/h5ls /usr/bin/h5mkgrp /usr/bin/h5redeploy /usr/bin/h5repack /usr/bin/h5repart /usr/bin/h5stat /usr/bin/h5unjam /usr/lib/libhdf5.settings /usr/lib/libhdf5.so.5 /usr/lib/libhdf5.so.5.0.0 /usr/lib/libhdf5_hl.so.0 /usr/lib/libhdf5_hl.so.0.0.0 /usr/share/doc/hdf5-1.8.0 /usr/share/doc/hdf5-1.8.0/COPYING /usr/share/doc/hdf5-1.8.0/README.txt libhdf5.so.5 and .5.0.0 and _hl.so.0 != what octave is looking for. I know EPEL isn't a CentOS project, IIRC, its a Fedora/RH projecct but this isn't looking good. JohnStanley Writes: That's strange because the both links I give you to them have on the down load page this; Provides : libhdf5.so.0 libhdf5_hl.so.0 Hdf5 Maybe try running "rpm --rebuilddb" or "ldconfig" or "yum clean-all" (bad or old yum headers can cause that)and then try the install again. Aonother thing to check may is your priorities for yum. Lastly it could just simply be the way the rpm was packaged. As in the developer has it going into a none standard directory or the other way around like Octave is looking for the lib in the wrong place. You could also take the two hdf rpms and compare the directory structure. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: ls and rm: "argument list too long"
On Sat, 2008-10-18 at 06:00 -0400, William L. Maltby wrote: > > The longest command line in this case is "find /usr -xdev', 15 > characters. Find "sees" only 10 characters. Uh, +1 for the \0 that terminates each parameter? Need more java here. > -- Bill ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: ls and rm: "argument list too long"
On Sat, 2008-10-18 at 06:00 -0400, William L. Maltby wrote:
>
Ok. 3rd cup of coffee has made its way into various of my systems. A
minor correction (but important for us pedantic typers) is below.
> main(argc, *argv[]) /* could be **argv instead */
main(int argc, char *argv[]) /* could be **argv instead */
> {
> /* stuff to do */
> .
> .
> .
> }
>
--
Bill
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] DHCP static hosts and subnet configuration
Marcus Wrote: I also wonder if it's really necessary to run two instances of DHCP with separate config files as dhcpd3 is able to detect the Subnets on which it may deploy leases, depending on the NIC configuration. JohnStanley Writes. The two commands I posted for you to set it up that way can be done in a Single File Configuration. The last config file I posted for you was for two NICS on two different Subnets. Now here is the catch because I know your saying it want work. Infact it will work. I just don't know or have an idea of the hardware you are using on your network. You will need what is called a dhcp relay client to forward dhcp requests to your dhcp server. That can obtained from any linux client on the that subnet you need to forward requests. See "man dhcrelay" That's the cheap way out. Next option would be to use a Nortel or Cisco Switch that can support VLAN so you can configure the the switches "ip helper-address" (interface) which in turn forwards the dhcp requests to the dhcp server. This is the thread I posted earlier for you. Pay no mind to the Ip addys. Substitute your own. You can add on to it also the static portion that you need for static clients. Should get you going atleast. http://lists.centos.org/pipermail/centos/2008-October/066615.html ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Re: ls and rm: "argument list too long"
Les Mikesell wrote:
Robert Nichols wrote:
These shouldn't make any difference. The limit is on the size of the
expanded shell command line.
Really?
$ M=0; N=0; for W in `find /usr -xdev 2>/dev/null`; do M=$(($M+1));
N=$(($N+${#W}+1)); done; echo $M $N
156304 7677373
vs.
$ /bin/echo `find /usr -xdev 2>/dev/null`
bash: /bin/echo: Argument list too long
For the first case, the shell never tries to pass the list as command
arguments.
It builds the list internally, limited only by memory size, and
processes the
words one by one.
Is that peculiar to bash? I thought the `command` construct was
expanded by shells into the command line before being evaluated.
I can't answer for how any particular shell allocates its internal memory,
but yes, the shell does read the entire output from `command` before
evaluating it. If this data is simply being used internally it never
gets passed to the kernel as an argument to exec() and thus can never
result in errno==E2BIG (7, "Argument list too long").
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ls and rm: "argument list too long"
On Oct 17, 2008, at 7:58 PM, thad wrote:
Satchel Paige - "Don't look back. Something might be gaining on you."
On Fri, Oct 17, 2008 at 4:36 AM, Laurent Wandrebeck
<[EMAIL PROTECTED]> wrote:
2008/10/17 Jussi Hirvi <[EMAIL PROTECTED]>:
Since when is there a limit in how long directory listings CentOS
can show
(ls), or how large directories can be removed (rm). It is really
annoying to
say, for example
rm -rf /var/amavis/tmp
and get only "argument list too long" as feedback.
Is there a way to go round this problem?
I have CentOS 5.2.
- Jussi
try something like:
for i in /var/amavis/tmp/*
do
rm -rf $i
done
it should be:
for i in `ls /var/amavis/tmp`
do
rm $i
done
___
Taking into account the valid objections others have mentioned, such
as problems of embedded whitespace in names, rm -rf $i and rm $i above
are not the same.
Even if there are no directories under the /var/amavis/tmp/, depending
on aliases, etc, rm $i may prompt you for confirmation. the other
will go ahead and do the remove if you have permission to do it (or at
least the -f).
The -r for files is unnecessary, and offends me when I see people do
it, but doesn't really cause any harm :)
I personally either rm -rf directory, and recreate the directory if
necessary, or do a find /var/amavis/tmp -type f ... because of
experience through the years with too long of command lines. Unixes
in the past had even smaller limits. xargs most frequently, and if
things fail, I may just do -exec rm -f {} \; on the find.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DHCP static hosts and subnet configuration
Dear John.
> The two commands I posted for you to set it up that way can be done in a
> Single File Configuration. The last config file I posted for you was for two
> NICS on two different Subnets.
I am not yet sure if we are talking about the same problem, so here is
my current configuration. Unless I add an host definition WITH
fixed-address statement to the 10.2.0.0 subnet, too LaptopWLAN won't
get an IP address within this network range.
...
authoritative;
ddns-update-style interim;
ddns-updates on;
update-static-leases true;
key "rndckey" {
algorithm hmac-md5;
secret "my-rndckey";
}
zone extra.net
{
primary 127.0.0.1;
key rndckey;
}
zone 2.10.in-addr.arpa
{
primary 127.0.0.1;
key rndckey;
}
zone intra.net
{
primary 127.0.0.1;
key rndckey;
}
zone 2.168.192.in-addr.arpa
{
primary 127.0.0.1;
key rndckey;
}
failover peer "intra-net" {
primary;
address 192.168.2.2;
port 647;
peer address 192.168.2.50;
peer port 647;
max-response-delay 60;
max-unacked-updates 10;
mclt 3600;
split 128;
load balance max seconds 3;
}
subnet 10.2.0.0 netmask 255.255.0.0
{
pool {
allow unknown-clients;
ignore client-updates;
deny dynamic bootp clients;
option routers 10.2.1.2;
option router-discovery false;
option domain-name "extra.net";
option domain-name-servers 10.2.1.2;
option ip-forwarding false;
option ntp-servers 10.2.1.2;
ddns-domainname "extra.net";
range 10.2.2.1 10.2.2.254;
}
}
subnet 192.168.2.0 netmask 255.255.255.0
{
pool {
failover peer "intra-net";
deny unknown-clients;
ignore client-updates;
deny dynamic bootp clients;
option routers 192.168.2.2;
option router-discovery false;
option domain-name "intra.net";
option domain-name-servers 192.168.2.2, 192.168.2.50;
option netbios-name-servers 192.168.2.50;
option netbios-dd-server 192.168.2.50;
option netbios-node-type 2;
option ip-forwarding false;
option ntp-servers 192.168.2.50;
ddns-domainname "intra.net";
range 192.168.2.150 192.168.2.151;
host LaptopWLAN {
hardware ethernet 00:15:17:17:0E:A8;
fixed-address 192.168.2.201;
ddns-hostname "LaptopWLAN";
}
# ... a LOT of other host declarations ...
}
}
...
Best Regards
Marcus
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] -bash: /bin/grep: cannot execute binary file
On Sat, Oct 18, 2008, Semih Gokalp wrote: > > Hi all,I have problem on CentOS 5.2 > while everything is working great,suddenly i have this error when i > login my server, This could well mean that your system has been cracked. These programs are frequently changed in common root exploits. You can run ``rpm -V packagename'' to check for package corruption: The command ``rpm -qf /bin/egrep'' will show the package name to which /bin/egrep belongs. A lazy way to handle this is: rpm -V `rpm -qf /bin/egrep` rpm -V `rpm -qf /bin/hostname` The most common reason these programs don't run after a root exploit is that the cracker has replaced them with binaries from another distribution and the binaries are looking for shared libraries that are not on the cracked system. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 "I do not feel obliged to believe that the same God who has endowed us with sense, reason, and intellect has intended us to forego their use." -- Galileo Galilei ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] -bash: /bin/grep: cannot execute binary file
On Sat, Oct 18, 2008 at 1:03 AM, Semih Gokalp <[EMAIL PROTECTED]> wrote: > > sudo su - What are you expecting this command to do? If you want to 'sudo' a command, do that. If you want to 'su,' do that. But don't mix the two together. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Thunderbird
On Thu, Oct 16, 2008 at 3:38 AM, ArcosCom Linux User <[EMAIL PROTECTED]> wrote: > On new CentOS 5.2 installation (and ugradation before config the diferent > programs I use), I'm having problems with Thunderbird 2.0.0.17. > Problem 1: > I configured my e-mail account (as I have in my old machine) and I have no > access to my pop3 and/or smtp servers. I write my user for the access, but > thunderbird no ask my password anytime. I am using Thunderbird 2.0.0.17 (20081001) on CentOS 5.2 (32 bit). I am using it with Gmail, using IMAP and SMTP. I do not have any problems with it. Please check all of your configuration settings, again, and verify that they are correct. You will get a pop up, asking for your password, if your POP3 or IMAP or SMTP server requires it, which it probably will. > Problem 2: > I installed lightning, but I can't add any new calendar to it (local or > remote). No idea what that is, so I can't help you on that one. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] -bash: /bin/grep: cannot execute binary file
On Sat, Oct 18, 2008 at 12:40:26PM -0700, MHR wrote: > On Sat, Oct 18, 2008 at 1:03 AM, Semih Gokalp <[EMAIL PROTECTED]> wrote: > > > > sudo su - > > What are you expecting this command to do? If you want to 'sudo' a > command, do that. If you want to 'su,' do that. But don't mix the > two together. I'm not the OP, but "sudo su -" is a very useful command; it gives the user full root access to a root shell with root's standard profile, but doesn't require them to know the root password. It's not good _security_ practice (not in a long way) but it can be a useful command. -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: DHCP static hosts and subnet configuration
John wrote: > Correct there. Classless Inter Domain Routing, never really got into doing > that. Do tell. > Largest I have dealt with was 1500 nodes and cidr is not needed there. Ermm. Classful routing is *dead*, CIDR is needed *everywhere*. > My main thing has always been getting a network provider to also provide > failover redudance. Had one dealing with lighting fiber and that was a > nightmare. Maybe I can get a few CIDR pointers from you. :-) http://www.faqs.org/rfcs/rfc1519.html - subnetting and such ... Ralph pgp2WzwasxQFi.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ls and rm: "argument list too long"
Jussi Hirvi a écrit : > Since when is there a limit in how long directory listings CentOS can show > (ls), or how large directories can be removed (rm). It is really annoying to > say, for example > > rm -rf /var/amavis/tmp > > and get only "argument list too long" as feedback. I doubt this. "argument list too long" is a shell error, and in your command the shell doesn't see many arguments. I guess you want to remove amavisd-new temp files and you did rm -rf /var/amavis/tmp/* In this case, the shell would need to replace that with rm -rf /var/amavis/tmp/foo1 /var/amavis/tmp/foo2 in which case, it needs to store these arguments in memory. so it would need to allocate enough memory for all these before passing them to the rm command. so a limitation is necessary to avoid consuming all your memory. This limitation exists on all unix systems that I have seen. > > Is there a way to go round this problem? > Since amavisd-new temp files have no spaces in them, you can do for f in in /var/amavis/tmp/*; do rm -rf $f; done (Here, the shell does the loop, so doesn't need to expand the list at once). alternatively, you could remove the whole directory (rm -rf /var/amavis/tmp) and recreate it (don't forget to reset the owner and permisions). > I have CentOS 5.2. > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ls and rm: "argument list too long"
On Oct 18, 2008, at 8:13 PM, mouss wrote: Jussi Hirvi a écrit : Since when is there a limit in how long directory listings CentOS can show (ls), or how large directories can be removed (rm). It is really annoying to say, for example rm -rf /var/amavis/tmp and get only "argument list too long" as feedback. I doubt this. "argument list too long" is a shell error, and in your command the shell doesn't see many arguments. I guess you want to remove amavisd-new temp files and you did rm -rf /var/amavis/tmp/* In this case, the shell would need to replace that with rm -rf /var/amavis/tmp/foo1 /var/amavis/tmp/foo2 in which case, it needs to store these arguments in memory. so it would need to allocate enough memory for all these before passing them to the rm command. so a limitation is necessary to avoid consuming all your memory. This limitation exists on all unix systems that I have seen. Is there a way to go round this problem? Since amavisd-new temp files have no spaces in them, you can do for f in in /var/amavis/tmp/*; do rm -rf $f; done (Here, the shell does the loop, so doesn't need to expand the list at once). alternatively, you could remove the whole directory (rm -rf /var/amavis/tmp) and recreate it (don't forget to reset the owner and permisions). I have CentOS 5.2. Possible to learn something new every day. I would have expected the for loop to fail too, thinking it would attempt to expand the wildcard before starting it's iteration. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ls and rm: "argument list too long"
> and get only "argument list too long" as feedback. > > Is there a way to go round this problem? > > I have CentOS 5.2. > I'm not going to repeat some of the good advice given to you by others as to how to avoid this error, but will instead tell you this is related to the ARG_MAX variable. The standard limit for linux kernels up to 2.6.22. is 131072 chars. This can be confirmed by typing: getconf ARG_MAX Until CentOS uses the 2.6.23 kernel (or later) in which the length of arguments is constrained only by system resources, you'll need to use scripting techniques which are more parsimonious. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Slow NFS writes
I guess I'm sort of surprised and I expected better performance I have a new server set up with RAID 10 drives (6) Repeated a number of times and though I am clumsy with stop watch timing, these numbers appear to be close enough for government work... Server, CentOS 5.2 and updated earlier today, just installed a week ago. Client, Macintosh G4, OS X 10.4.11 NFS Mount is done with the following options... -P (privileged ports) intr -r=32768 -w=32768 I tried doubling the size of the read/write windows to 65536 but it seemed to make little difference. Task, Read / Write 648 Megabyte Photoshop file (PSD) Win2K = Win2K server (slow), RAID 5, Symantec EndPoint (ugh), retiring this server AFP = Netatalk from new CentOS Server SMB = Samba from new CentOS Server NFS = see above options, same CentOS Server Copy To Win2K AFP SMB NFS 1m40.053s 0m22.566s 0m23.817s 2m11.849s Copy From Win2K AFP SMB NFS 1m34.478s 0m20.709s 0m20.823s 0m23.487s NFS read performance was slightly slower than AFP/SMB but the write performance was poor. I suppose that the answer is not so important because if the performance was equal to AFP and/or SMB, they'd probably just use AFP anyway but I did want to register my shock (or my ignorance). Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
