| Linux Forum Index » Linux Miscellaneous Topics » Vbox... |
|
Page 1 of 1 |
|
| Author |
Message |
| Van Chocstraw... |
 Posted: Thu Feb 05, 2009 6:15 pm |
|
|
|
Guest
|
I can make it go full screen but my vm (Win7) stays half size and
doesn't go full screen. How can I make that go full screen too.
--
<<//--------------------\\>>
Van Chocstraw
>>\\--------------------//<< |
|
|
| Back to top |
|
|
|
| Stefan Patric... |
| Posted: Fri Feb 06, 2009 3:43 pm |
|
|
|
Guest
|
On Thu, 05 Feb 2009 17:15:01 -0500, Van Chocstraw wrote:
Quote: I can make it go full screen but my vm (Win7) stays half size and
doesn't go full screen. How can I make that go full screen too.
Just a guess: check the Display size in Win7's Control Panel.
Stef |
|
|
| Back to top |
|
|
|
| TomB... |
| Posted: Sun Feb 08, 2009 2:24 pm |
|
|
|
Guest
|
On 2009-02-05, Van Chocstraw was urged to write the following:
Quote: I can make it go full screen but my vm (Win7) stays half size and
doesn't go full screen. How can I make that go full screen too.
You should install the correct display drivers. I don't think there
are any for W7 yet. |
|
|
| Back to top |
|
|
|
| Tech Geek... |
| Posted: Mon Feb 09, 2009 5:01 pm |
|
|
|
Guest
|
Hi,
We have about 125 Linux(RH)/Unix(Solaris) servers and to be in line with the
security policy we have to change our password every 90 days. How can I
change the password on all the server in an automated fashion....I can use
ssh. Please help me with options.
Thanks in advance. |
|
|
| Back to top |
|
|
|
| Scott Lurndal... |
| Posted: Mon Feb 09, 2009 6:27 pm |
|
|
|
Guest
|
"Tech Geek" <tech_geek at (no spam) verizon.net> writes:
Quote: Hi,
We have about 125 Linux(RH)/Unix(Solaris) servers and to be in line with the
security policy we have to change our password every 90 days. How can I
change the password on all the server in an automated fashion....I can use
ssh. Please help me with options.
Thanks in advance.
Wouldn't it be easier to use NIS+, LDAP or even AD?
scott |
|
|
| Back to top |
|
|
|
| Tech Geek... |
| Posted: Mon Feb 09, 2009 9:20 pm |
|
|
|
Guest
|
"Scott Lurndal" <scott at (no spam) slp53.sl.home> wrote in message
news:4990adc3$0$28005$6c36adad at (no spam) news.usenetserver.com...
Quote: "Tech Geek" <tech_geek at (no spam) verizon.net> writes:
Hi,
We have about 125 Linux(RH)/Unix(Solaris) servers and to be in line with
the
security policy we have to change our password every 90 days. How can I
change the password on all the server in an automated fashion....I can use
ssh. Please help me with options.
Thanks in advance.
Wouldn't it be easier to use NIS+, LDAP or even AD?
scott
Scott,
thanks for he response....we did try LDAP but couldn't be implemented
successfully because of apparent conflicts the cluster software is having
with the existence of LDAP. We had to disable LDAP to allow the cluster
software to work. We have been working with the vendors but we haven't
gotten a working resolution yet.
Thanks again. |
|
|
| Back to top |
|
|
|
| Keith Keller... |
| Posted: Mon Feb 09, 2009 11:46 pm |
|
|
|
Guest
|
["Followup-To:" header set to comp.os.linux.admin.]
On 2009-02-10, Tech Geek <tech_geek at (no spam) verizon.net> wrote:
Quote:
thanks for he response....we did try LDAP but couldn't be implemented
successfully because of apparent conflicts the cluster software is having
with the existence of LDAP. We had to disable LDAP to allow the cluster
software to work. We have been working with the vendors but we haven't
gotten a working resolution yet.
That sounds pretty unbelievable. Software should not be interacting
with the authentication mechanisms directly, so LDAP or no LDAP should
make no difference.
One thought occurs to me: are the compute nodes on the cluster on their
own private switch? If so they likely can't get to the LDAP server.
One potential way around this would be to make the head node an LDAP
slave, and configure the compute nodes to get their LDAP information
from the head node instead of the master LDAP server.
Other folks suggested NIS. Unless your network is firewalled well, and
your internal users are trusted, NIS is a security nightmare. LDAP will
serve much better.
--keith
--
kkeller-usenet at (no spam) wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information |
|
|
| Back to top |
|
|
|
| jellybean stonerfish... |
| Posted: Tue Feb 10, 2009 1:41 am |
|
|
|
Guest
|
On Tue, 10 Feb 2009 01:23:06 +0000, Tech Geek way over crossposted.
Quote: Thanks for the response and information. Not sure why we didn't
implement NIS...I will check this out. As regards copying the password
file and shadow files...doesn't it require root access.
If you want to change the password file, then you are going to need
root access. If you can use ssh, then you can use scp. If host1 has the
new password file, and you want to send it to host2.
scp host1:/etc/shadow host2:/etc/shadow
Quote: I haven't done
this (I am not a Sys Admin!)
If you are given the task of maintaining the passwords of 125 machines,
then you are now a "Sys Admin".
Quote: .,...will this approach allow copying over
the shadow file entries only for one user?
You can change one line. For example if I grep for the username "guest"
I will see the line with the quest password.
grep guest /etc/shadow
guest:$1$Le8tyxs2$CEV9tQNxxYr5aLJVXkvHX1:14011:0:99999:7:::
The password string is right after the username and a ":" character
A short sed command can change the string into a newstring.
sed -i 's/guest:[^:]*:/guest:newstring:/' shadow
Quote: Will it be possible to help
me some more additional information on this approach. Appreciate your
time and help with this.
|
|
|
| Back to top |
|
|
|
|
