I am using CentOS 5.5 and I created few users (useradd john etc.) and now I want to assign privileges to this user on some directories and files in those directories. For example I want to give read privileges to directory "/documents" and all of files under that directory.
i searched the forum about this subject, i found many post but nothing useful. i also wonder why a normal user is not prompted to authenticate as root to perform these tasks. i thought the file /etc/sudoers but i don't think this is the point. i tried the group "shutdown" but does not exist. i read that this is expected in ubuntu server so it should exist even in the desktop version, i guess.
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27) reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59) 09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this Code: shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40) reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59) 09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip] reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54) shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05) wtmp begins Thu Mar 11 08:25:26 2010 [snip] reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42) shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13) [snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
In researching current ldap issue (not being able to do anything but log in) it seems that there are no concepts of privileges, roles, etc. that could be assigned to a user in LDAP.
I've only seen fields that deal with name, organization, etc., not with application-specific access control.
I have to assign certain access privileges to users authenticated via LDAP server based on the privilege level mentoned in the LDAP server. How to attain this.
I need to create a user in Fedora Linux(15) which only has privileges to print documents.Our college issues a printer to each lab and I need to create a new user on my Fedora which only has privileges to print.Network sharing is not an option, so is there any way by which I can a restrict a user from executing any commands except the necessary printing commands?
I want to create a user who has all the privileges that root user has.I know how to create a user but i don't know how to grant root privileges to him.
I create a user in CentOS 5.5 for using with my email account.
useradd ralf passwd ralf
use "ralf user" only for my email account. How can I remove others privileges/permissions? Also, I want to use "ralf user" without root privileges/permissions.
I need to create a special linux user account that has a very limited set of permissions on the system. Essentially to have read-only permissions for his home dir (and sub dirs) and nothing else - i.e. this user has no write or execute permissions and should not be able to read/access other user dirs or indeed anything outside of his home directory, irrespective of rwx permissions.
How to allow access to some commands having root privleges to be run by non root user. I am new to unix/linux and I have a major assignment. I have to find ways to run particular commands which can be run only by root from a non root user. I know sudo is one of the way but i need some different approach.
All of as now the add-to-panel item that via it you can shutdown the PC without the need of typing any password to gain root privileges.
How is this possible? I know that fro default the login screen is run by root but how do this app sends the signal to the login-screen to shutdown? I mean, this app is run without root privileges by me, the simple user, and when clicked the PC shutdowns via a signal from this app to the login screen.... How can I call this signal to an app of mine?
I want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
in configuring a fresh install of Squeeze. I discovered that it is possible to power off the system under gnome simply by pressing the power button or by selecting the "Shut Down" entry on "System" menu.However I need to restrict this option only to root. How can I do that?
This applies to users of 10.04 (64 bit), but I would like to hear from those running 10.04 (32 bit) and 9.10 (64 or 32 bit).Would you be good enough to answer this question: Do you have an �enable scanner option� (or a variation of that phrase) in (GOTO) System-Administration-Users & Groups- [Your Admin Account]- Advanced Settings- User Privileges?It would be immensely helpful of you if you could do this and post me your answer.
I often get responses from people who first say: "Are you sure? You want your network to be exposed to the outside world?" I am not experimenting on a Production Server of NASA or any Security Concern Department. Friends, there is no harm in experimenting on your personal computer or on a test computer which is isolated from the production environment. Look at hackers! What do they do? If they don't know how security is breached then how would they come up with security measures?
If my question reads... "How to let any user perform Administrative Tasks on a Linux System irrespective of his/her privileges on that particular system?" then I would not get the right answers in the first place. They will say... "You are letting everyone destroy your system... are you sure you want to do that?" My question is: Why should we restrict ourselves from experimenting even if it sounds weird to other people?
I give you an example where it is desirable to let an unprivileged user perform certain tasks. You want to know if there are any employees in your office who are storing videos in their home directory and filling up the disk space to a great amount. You have a department called "Command Center or Data Center Operations or Help Desk" call it whatever you would, whose work is to monitor such activities, and you create an account "monitor" for them to monitor such activities but they are not able to do them:
I have found so many ways for root user to execute commands in so many possible path locations - but having difficulties on executing commands as normal user - during start up.This is what i've got for /etc/rc.d/rc.local script:Code:su -l user && (/bin/sh svc_cmd.sh &)But the command doesn't run at all...
I have a small problem on ubuntu 10.04, of which i know it can be solved. However, i'm not sure how to. The problem is; I need one user to be able to install updates, but not give it any other privileges. I have been messing around with the "sudoers" file in /etc a bit, and thought i needed to use the "NOPASSWD" But i'm not sure what to do after that.
I accidentally promoted my initial account to admin and now I want to revert it but I don't remember the specific initial user privileges.So there are 2 questions:
1) First, is it safe to "downgrade" the account, logging in with another one? In general what's the best way to do it?
2) Could someone enter Administration->Users and Groups->[select initial account]-> Advanced Settings->User Privileges and list the privileges that are on by default?
I repeat I want the privileges of the initial account, which I suspect are above those of basic users (that are added later) and below admin...
I'm using ubuntu 10.04. Apache server is associated with www-data.I frequently run into problems editing or deleting files created by a cgi script, as they have ownership of www-data:www-data.How can I safely modify my system so that the output files are editable or deletable by user tim?