- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Installing top
Operating System - Tru64 Unix
1761307
Members
3204
Online
108901
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2008 06:55 AM
тАО11-09-2008 06:55 AM
Installing top
I tried to install the latest "top", top3.8, on my 5.1B-4.
Two issues:
I had to
# chmod a+r /dev/mem
# chmod a+r /dev/kmem
and
# chmod u+s /usr/local/bin/top
to make it work for normal users.
Is this safe?
Or are there any alternatives?
Two issues:
I had to
# chmod a+r /dev/mem
# chmod a+r /dev/kmem
and
# chmod u+s /usr/local/bin/top
to make it work for normal users.
Is this safe?
Or are there any alternatives?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2008 11:16 AM
тАО11-09-2008 11:16 AM
Re: Installing top
> I tried to install the latest "top",
> top3.8, on my 5.1B-4.
Really? Where did you find it? The latest
I could find said that it was "Top version
3.8beta1".
What, exactly, does "tried to install" mean?
> I had to [...] and [...]
I doubt it. Around here, using "Top version
3.7", "chmod u+s /usr/local/bin/top" seems to
be enough. Changing the permissions on those
/dev/*mem files sounds unwise to me.
With:
urtx# ls -l /dev/*mem
cr--r----- 1 root mem 2, 1 Jan 27 2006 /dev/kmem
cr--r----- 1 root mem 2, 0 Jan 27 2006 /dev/mem
you could do somethings like:
chgrp mem /usr/local/bin/top
chmod g+s /usr/local/bin/top
to get around these permission problems, but
if you expect to get the process info, then
those won't be enough, but "chmod u+s"
(alone) should be enough.
Around here, README says:
On some systems, top requires read access to the memory files
"/dev/kmem" and "/dev/mem" as well as the system's kernel image. Most
installations have these files protected from general access. These
sites would have to install this program in the same way that programs
such as "ps" are installed. On most systems with a /proc file system,
top will try to read everything it can from /proc, but may need extra
permissions to do so. The configure script will determine the
permissions needed by the top binary, and a "make install" as root
will get the binary installed correctly. Sometimes this requires that
the binary be installed with set-group-id privileges and, in rare
cases, set-user-id to root.
Well, around here:
urtx# ls -l /sbin/ps
-rws--x--x 1 root bin 123360 Dec 5 2006 /sbin/ps
The "configure" script may not correctly
"determine the permissions needed by the top
binary", but the other guidance provided by
README seems to be pretty good.
> top3.8, on my 5.1B-4.
Really? Where did you find it? The latest
I could find said that it was "Top version
3.8beta1".
What, exactly, does "tried to install" mean?
> I had to [...] and [...]
I doubt it. Around here, using "Top version
3.7", "chmod u+s /usr/local/bin/top" seems to
be enough. Changing the permissions on those
/dev/*mem files sounds unwise to me.
With:
urtx# ls -l /dev/*mem
cr--r----- 1 root mem 2, 1 Jan 27 2006 /dev/kmem
cr--r----- 1 root mem 2, 0 Jan 27 2006 /dev/mem
you could do somethings like:
chgrp mem /usr/local/bin/top
chmod g+s /usr/local/bin/top
to get around these permission problems, but
if you expect to get the process info, then
those won't be enough, but "chmod u+s"
(alone) should be enough.
Around here, README says:
On some systems, top requires read access to the memory files
"/dev/kmem" and "/dev/mem" as well as the system's kernel image. Most
installations have these files protected from general access. These
sites would have to install this program in the same way that programs
such as "ps" are installed. On most systems with a /proc file system,
top will try to read everything it can from /proc, but may need extra
permissions to do so. The configure script will determine the
permissions needed by the top binary, and a "make install" as root
will get the binary installed correctly. Sometimes this requires that
the binary be installed with set-group-id privileges and, in rare
cases, set-user-id to root.
Well, around here:
urtx# ls -l /sbin/ps
-rws--x--x 1 root bin 123360 Dec 5 2006 /sbin/ps
The "configure" script may not correctly
"determine the permissions needed by the top
binary", but the other guidance provided by
README seems to be pretty good.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2008 11:33 AM
тАО11-09-2008 11:33 AM
Re: Installing top
You are right, it was top3.8beta1, sorry about that.
"Tried" ment that it did not build and run right away, I had to tweak the build a little bit. Make install worked, of course.
As a user, I got permission error on /dev/kmem and /dev/mem, so I opened the read permission to all.
Then it ran but no processes were shown, only the header part.
So I chmod s+u /usr/local/bin/top as adviced in the docs.
But I forgot to try without the open read permissions at this stage, thanks for pointing this out.
I set the permissions back to original and it still runs as it should.
Thanks.
"Tried" ment that it did not build and run right away, I had to tweak the build a little bit. Make install worked, of course.
As a user, I got permission error on /dev/kmem and /dev/mem, so I opened the read permission to all.
Then it ran but no processes were shown, only the header part.
So I chmod s+u /usr/local/bin/top as adviced in the docs.
But I forgot to try without the open read permissions at this stage, thanks for pointing this out.
I set the permissions back to original and it still runs as it should.
Thanks.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP