|
|
Subject: SUMMARY: [2] veritas vs ufs performance comparison - msg#00042
List: os.solaris.managers.summaries
On Thu, Sep 11, 2003 at 01:56:34PM +0000, Przemyslaw_Bak@xxxxxxxxxx wrote:
> Thanks all who responded.
> In general there are two documents (in fact three) which compares
> VxFS to UFS. But it was foreseeable that doc from SUN says that UFS
> is faster then VxFS and document from Veritas says that ... guess what :-)
Sorry for not including URL/docs.
Here you are:
http://seer.support.veritas.com/docs/252302.htm
Another as attachment.
przemol
[demime 1.01b removed an attachment of type application/pdf]
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Summary: native ldap and sudo
Thanks to jrwren@xxxxxxxxxxx, who provided the
following hints, which worked.
My original question was how to make sudo work with
the Solaris 9 ldap client (with password aging
enabled).
Thanks!
> If you are using sudo from sunfreeware, it is not
> compiled with PAM
> support, thus it reads its password information
> directly from the
> shadow file. Solaris LDAP auth is achieved through
> the PAM facility.
>
> Try recompiling sudo yourself with the --with-pam
> flag.
>
> It worked for me using the padl LDAP utils.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Next Message by Date:
click to view message preview
preliminary SUMMARY Problems with some UIDs
Thanks to:
Caspar Dik
Michael J Watson
Reggie Beaver
Matthew Stier
James Zhao
A couple of suggestions here are to:
zap the /var/adm/lastlogin as this could have some spurious entries in it.
restart the Naming Service Cache Daemon in it.
I shall give these a try next time the problem crops up.
For information, the user simply gets a momentary message that they are not
permitted to log on before closing their session. We are also using telnet
rather than rlogin so there are no issues with .rhosts.
Another suggestion is that some packages could be messing up the permissions
on /etc/passwd and /etc/shadow. We have not recently installed any packages
on this system and it does not affect all users. Another suggestion was
that there may be a restricitve umask somewhere though this is also standard
for all users.
Thanks for the suggestions and I will give another update when the next user
crops up.
Regards
Roger
Roger Kynaston
UNIX Systems Analyst
Information Technology Services
Policy and Administration
London Borough Hammersmith & Fulham
Tel. 0208 753 2919
email: roger.kynaston@xxxxxxxxxxx
The information contained in this e-mail is intended for the recipient or
entity to whom it is addressed. It may contain confidential information that
is exempt from disclosure by law and if you are not the intended recipient,
you must not copy, distribute or take any act in reliance on it. If you have
received this e-mail in error, please notify the sender immediately and
delete from your system.
Previous Message by Thread:
click to view message preview
Summary: native ldap and sudo
Thanks to jrwren@xxxxxxxxxxx, who provided the
following hints, which worked.
My original question was how to make sudo work with
the Solaris 9 ldap client (with password aging
enabled).
Thanks!
> If you are using sudo from sunfreeware, it is not
> compiled with PAM
> support, thus it reads its password information
> directly from the
> shadow file. Solaris LDAP auth is achieved through
> the PAM facility.
>
> Try recompiling sudo yourself with the --with-pam
> flag.
>
> It worked for me using the padl LDAP utils.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Next Message by Thread:
click to view message preview
preliminary SUMMARY Problems with some UIDs
Thanks to:
Caspar Dik
Michael J Watson
Reggie Beaver
Matthew Stier
James Zhao
A couple of suggestions here are to:
zap the /var/adm/lastlogin as this could have some spurious entries in it.
restart the Naming Service Cache Daemon in it.
I shall give these a try next time the problem crops up.
For information, the user simply gets a momentary message that they are not
permitted to log on before closing their session. We are also using telnet
rather than rlogin so there are no issues with .rhosts.
Another suggestion is that some packages could be messing up the permissions
on /etc/passwd and /etc/shadow. We have not recently installed any packages
on this system and it does not affect all users. Another suggestion was
that there may be a restricitve umask somewhere though this is also standard
for all users.
Thanks for the suggestions and I will give another update when the next user
crops up.
Regards
Roger
Roger Kynaston
UNIX Systems Analyst
Information Technology Services
Policy and Administration
London Borough Hammersmith & Fulham
Tel. 0208 753 2919
email: roger.kynaston@xxxxxxxxxxx
The information contained in this e-mail is intended for the recipient or
entity to whom it is addressed. It may contain confidential information that
is exempt from disclosure by law and if you are not the intended recipient,
you must not copy, distribute or take any act in reliance on it. If you have
received this e-mail in error, please notify the sender immediately and
delete from your system.
|
|