Ubuntu :: Get Root Script To Run A Command As Normal User?
Jun 8, 2010
Because I have a flaky wireless device, I occasionally get a hung connection and this script gets things running again in just a few seconds except obviously the boldfaced item, as it still tries to run in the root directory and gives errors:
Configuration file "/root/.kde/share/config/knetworkmanagerrc" not writable.
Please contact your system administrator.
So I am not sure how to get knetworkmanager to run as me, the user ubuntu in the /home/ubuntu directory
#!/bin/bash
service network-manager stop
sleep 1
killall -9 knetworkmanager
I would like to allow normal users to run some root scripts (e.g the sound subsytem [alsa]) in cases sound is stuck. What is the best way to allow this to happen in opensuse? There are many ways to do that (and I do not know how to use any of them ) and I am not sure which one is more suse all right.
I'm trying to get my backup script to run every week, but as a normal user, and not as root as it is done when the script is placed in /etc/cron.weekly. Anacron fits my needs in the sense that it doesn't require my computer to always be on, as opposed to cron, and will just run my script when it can, but at the most each week. Cron fits my needs in the sense that I can run the script as the user I am logged in as. The particular script backs up my home directory with rdiff-backup, and it is very convenient that I am the owner of that backup, since when root performs the backup, I am unable to browse my own backup files and must use "sudo" to do this.
Is there a way to let me use the feature of anacron that allows my computer to not always be on, but still get a weekly execution, and also run the script as a normal (non-root) user?
I am using fedora 12.I have two internal drives. Both are ntfs. Whenever i click on them it prompts to enter root password. But i want to mount them as normal user without entering any root password. How can i disable it so that i am not asked to enter root password everytime i mount the drives.
I'm using fedora 12 and modified the user login options(normal and super user login). I've been using the accounts for a while but i've bumped into a problem - audio not working as a normal user but works when logged in as root. Also, i'm not able to use VLC as a root user.
On a Fedora Core box, I have a normal non-privileged user and I also have sole access to the root account. Because I am the only administrator of this box, I frequently su over to root for administrative tasks. The problem is that many of the user configuration I've become accustomed to are only configured on my day-to-day account (.vimrc, .bashrc, .screenrc, etc). Other than giving my day-to-day user account privileges to perform administration tasks, how would I go about sharing configuration between these two accounts?
i am looking for a detailed description of the login process for both root and normal user , also locally and remotely.i read some sentences that the files .bashrc and bash_profile are needed for this process. But that was very concise.
I would like to be able to suspend to disk or Ram from the command line. I can do it with the package 'hibernate' which works well, but it needs to be run as root:
Code:
Do you know if there is any way that I can make this script run by normal users?
I am using a minimal version of 9.04 with openbox.
I'm setting up Ubuntu Karmic on my sister's old computer for my nephew, he's quite young so my sister asked to install some content filtering. I'll first setup an OpenDNS account and I've installed and managed to get dansguardian and squid working on a virtual machine to try it out. so far it's working pretty well, but I need to secure it form the inside out.
I was thinking of blocking specific outbound ports so he could not bypass the proxy. because by default the firefox configuration can be easily changed. so I have a couple of questions.
1. is it possible to block outgoing ports on Ubuntu? 2. is that the best method? 3. is there anything else I should be aware of to prevent subversion?
lastly, this question is probably unrelated to this board but I've set up a cron job to update a dynamic ip with OpenDNS, the problem is that the password is in clear text in the user's crontab, can I play with permissions? is it possible to run the job under a root account and deny read/write access to a normal user?
I'm trying to start an Oracle Integration server as user "oracle" at system startup and my approach was to place a couple of lines in /etc/rc.localsu oracle/home/oracle/startallSomething is not quite right about this as it seems to leave some processes owned by root.
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 am using vicidialnow 1.2 VERSION: 2.0.4-122 and BUILD: 81011-0855 (CEntos Based Dialer). In all the way, it is working fine. I want to give the access of command /usr/sbin/mtr to a Normal System USer, which is not working according to my wish. I have make the entry in as sudo or make the soft link of /usr/sbin/mtr to /bin. But all in vain. And i am not in the condition to give the root access to the user.
The normal user is now in the sudoers group. How can i allow it to install programs using it's own password rather than having to know the super-secret Root-Users password?
when loggin as a normal user and search for a file passwd under /etc. i get few errors with permission denied.how to ignore this permission denied errors.
I've got a custom compiled kernel, just built on Lucid 10.04 from the kernel sources.System works fine, except for sound.When I log in as normal user and try to play a wav file using.The sound file is being played, but I hear no sound.However, when I do "sudo -s" and become root, execute the same mplayer command then I can hear the sound.My Sound preferences shows no input device and only "Dummy Output" as output device.On the generic kernel as came with the Lucid 10.04 CD, sound preferences shows different devices.The strange thing is: when I compiled my custom kernel, I changed nothing to the sound options in the kernel config file.
I have a Red Hat 4 server with Sungard Luminis installed on it. I was following some instructions on setting up Luminis to start at boot. One of the steps was modifying the sudoers file. Since modifying the sudores file, I am no longer able to "su" to root when logged in as a normal user. When doing so, I get su: incorrect password after putting in the password. I have another server with the exact same setup, broken one is test, the other is production, that works just fine. I made no changes to my production server. I've been looking at different things all day and the only difference I have found between the two are the results I get from running rpm -q --verify coreutils. Running that on my prodution server returns nothing. Results from my test server are below. Is this what is causing my problems? If so, what's the fix? I haven't found that yet. I've checked /etc/pam.d/su, both servers are the same.
So, i've a little question. I have a Linux Red Hat 5.1 System wich has a programm that needs to be started as a user -> usera .When i reboot the server, how can i make it possible to run a command in the shell as usera user?Someone told me, that this is not possible to make an autostart entry because this works only with the root account?!What i want its simple.- Command -> startprg need's to be started as user usera automatically after an automated reboot of the red hat linux
I was wondering if someone had a logical reason and therefore complete, hopefully that makes total sense, for why when I install Ubuntu I cannot use the 'sudo' command either with root or user passwords. Even if I try to edit the permissions for sudoers, I still recieve an error message that says access is denied and so as the root user on my pc I don't understand why I can't put my name in the sudoers file or use the sudo command with the correct password.
Why we have to log in as root user some times while we can use sudo in command line ,is it diffrent , does sudo dont have all access and all permessions? i am really lost , i know little of alot of things in ubuntu ,but still missong alot of circles to make the complate picture.
I am a Fedora user and have recently shifted to Debian.I tried to install httperf using the following command as root user:apt-get install httperfbut apt-get cannot locate the package:
root@D6-VM:/home/saad# apt-get install httperf Reading package lists... Done Building dependency tree
When I log on a root and attempt to issue the command Freshclam to upgrade the virus definitions it attempts or create a new file with a definition name. I get a message stating that the directory isnt writable. The user and group access rights are as follows:
USER = read, write, execute Group = read, write, execute All= read, execute.
The only way I can get around this is by applying a 777 which would be read, write and execute for all. Now, I have a group define with several user ids in it including Root.How do I connect the group with the directory/file so I dont have to apply a 777 access right to group users could issue the Freshclam command.
I have a question that i want to make a normal user to execute the commands which the root user is able to execute, say if i have a user named siru and when i logged in using siru i cannot run commands like tracert,nmap@loccalhost and all but i can run when i have logged into root account so my question is how to make siru to run the command tracert,nmap@localhost.I have even edited the .bash_profile of siru's home directory from
# .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then
Is there a non-root shell command that can tell me if a user's account is disabled or not? note that there is a fine distinction between LOCKING and DISABLED:
LOCKING is where you prepend ! or * or !! to the password field of the /etc/passwd file. On Linux systems that shadow the passwords, this marker flag may be placed in /etc/shadow instead of /etc/passwd. Password locking can be done (at a shell prompt) via password -l username (as root) to lock the account of username, and the use of the option -u will unlock it.
DISABLING an account is done by setting the expiration time of the user account to some point in the past. This can be done with chage -E 0 username, which sets the expiration date to 0 days after the Unix epoch. Setting it to -1 will disable the use of the expiration date.
The effect of locking to to prevent the login process from using a supplied password to hash correctly against the saved hash (by virtue of the fact that the pre-pended marker character(s) are not valid output character(s) for the hash, thus no possible input can ever be used to generate a hash that would match it). The effect of disabling is to prevent any process from using an account because the expiration date of the account has already passed.For my situation, the use of locking is not sufficient because a user might still be able to login, e.g. using ssh authentication tokens, and processes under that user can still spawn other processes. Thus, we have accounts that are enabled or disabled, not just locked. We already know how to disable and enable the account - it requires root access and the use of chage, as shown above.To repeat my question: is there a shell command which can be run without root privileges which can output the status of this account expiration info for a given user? this is intended for use on a Red Hat Enterprise 5.4 system.The output is being returned to a java process which can then parse the output as needed, or make use of the return code.
