Hi,
this time it seems to be 'in topic'
I justb wrote to the security list my mail about accessing a Win2k-pc (subj.
Win2k within a Linux-Lan)
and I received it allready back from the list, that's ok!
BUT at the same time I got an infromation that exactly this mail (abs. same
content) could not have been delivered to another address
martens(a)prointernet.de:
Final-Recipient: rfc822;d.martens(a)prointernet.de
Action: failed
Status: 5.2.1
X-Display-Name: Dominik Martens
It looks as if copies of my mails are automatically sent to a second address!!
Can that be has anybody an idea, what has happend?
It is from a new pc with newly installed SuSE 8.2
Carl
Hi list,
glibc-2.2.5-177 update (is 184 version the same thing?)
has RPC fixes if I did read correctly from SuSE www pages.
My problem is that upgrading from version 164 seems to
cause a huge delay in starting up my JBoss application.
An initial context lookup related initialization that used
to take about 3.3 seconds with the version "164" now takes
about 33 seconds (10 times that of the earlier version).
I think there is glibc dependence as I checked this with applying:
rpm --force -Uvh i386/update/8.1/rpm/i686/glibc-2.2.5-164.i686.rpm
and re-running the application: back to 3.3 seconds.
All this when the stuff goes over network. If the application is run in
the same machine as the EJB server then I get more or less the
better results (about 2.8 seconds).
I could be totally wrong with this but I still want to try finding out
if someone else has already found a fix/solution. I didn't yet dive into
the source of glibc-2.2.5 but I will do that next unless faster solutions
exists. (Of course downgrading is some option too).
java -version reports:
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)
any hints, anybody?
regards,
timo
Hi,
may be s.o. can help me off the list - it's not totally the topic of that
list.
I have to run Win2k within a Linux-LAN. It allready runs behind a Linux
Firewall without any problems (gateway, routing, ..)
But now I have installed a program that connects Win-DDE to a socket and I
want to access this socket.
Well from Win2K I can ping all pc,
but from the linux-pc I can't ping the Win2K-pc nor can I access the socket:
no route to that pc.
Any idea what (and where) I have to set what variables, data, to be able to
access that pc?
Thanks so far,
carl
Hi,
I've got some machines running as NIS clients very fine. Files like hosts,
networks, auto.master, ... are used by all these machines. The passwd-file is
also allocated by NIS and I can change the passwd by yppasswd an some
minutes later I have the new password on all other machines. Everything is fine,
but there is one thing I cannot change and maybe it's just a small entry in one
configuration-file.
The NIS server should be a NIS client at the same time so that I can logon
to my NIS server by using the same password as I use for the NIS clients. I
configured all files in the same way as I configured the other client machines
but when I log on the server I have to give the password I gave the server
when I installed the linux system. Using passwd (or yppasswd) on the server
will change the NIS password so that I have to login on every nis client with
the new apssword except the server/client. I don't see any possibility to
change this password (or to login to server using the same password I am using for
the clients).
One more thing attract my attention: In the nsswitch.conf file the order to
lookup for the passwd is 'nis files'. I can login my server by using the
'local' passwd (not the nis passwd). If I delete the 'files' entry, so that all
passwds should be talken from nis it makes no differences. But, I am not able
to change to root any longer (whcih seems to be normal).
Maybe someone can help me ? Or do you have a good link to get a solution for
this ?
Thanks, ...
...niels.
Here are some of my configurations:
Using SuSE 8.2 on alle machines.
The 'domainname' is the same on all machines.
/etc/nsswitch.conf (on all machines):
passwd: nis files
shadow: nis files
group: nis files
hosts: nis [NOTFOUND=return] files
networks: nis [NOTFOUND=return] files
...
yp.conf contains the IP of the server or 127.0.0.1 (on all machines)
/var/yp/securenets allows access for
255.0.0.0 127.0.0.0
255.255.255.224 192.168.200.0
/etc/passwd contains no 'normal users'. The last line is +:::::: (same for
file /etc/group)
/etc/nis/passwd contains all 'normal users' and /var/yp/Makefile includes
/etc/nis for passwd, shadow and groups.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
