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
[code]....
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
View 4 Replies View Relatedi am having problems with privileges i have created a new user with my name, but i cant get root privileges on it. i need the same privileges as the root profile.
View 9 Replies View RelatedBecause 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
[code]....
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.
View 9 Replies View RelatedWhy 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.
View 8 Replies View RelatedWhen 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.
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.
Is It possible to change a process running in root-user to non-root-user by setting suid / uid / euid / gid etc... I so please instruct how, when and wat to set in order to change a process running in root-user to non-root user
View 4 Replies View RelatedSince upgrading my Debian/unstable amd64 installation a few days back I can no longer log in as either root or user, whether to SDDM, via the console, or via ssh. When trying with the console, I can see the login message flash briefly on the screen, before the console resets itself.
I can boot into recovery mode, and examine log files. I enabled systemd debug logging and, amid reams of messages, these seem the most pertinent:
Sep 25 02:24:43 cooler systemd[1]: Received SIGCHLD from PID 937 (login).
Sep 25 02:24:43 cooler systemd[1]: Child 937 (login) died (code=killed, status=6/ABRT)
I just setup a debian OS(in emulator) and trying to use apt-get update. When I log in as root and do:
export http_proxy=http://proxy.com:9090
apt-get update works
If I use another user and ssh to this debian, sudo apt-get update will fail to work because it don't use the proxy. I try to do the export http_proxy stuff again but still not working. echo $http_proxy showing it already set correctly...
p/s:
I have a workaround by adding this lines in the apt.conf
ACQUIRE {
http::proxy "http://proxy.com:9090"
}
but I really don't want this solutions because I want to easily disable the http_proxy in command prompt (by unset it).
I accisentaly deleted my root user on lenny, because of a gamepanel...Do you know how to re-create it?I am logged in SSH with the root user, so i'll try to re-enable it when the work will end in the window.Edit:User now re-created, he doesnt have the root rights
View 4 Replies View RelatedI'm trying to familiarize myself with LXDE to help a friend of mine and one thing I just cannot solve, despite many googles, is how to allow a non-root user to auto-mount drives in the left-hand pane of PCMANFM.Everything works just fine as long as I have the root passwd. Not a huge problem but very irritating none-the-less.
View 9 Replies View RelatedI'm on Squeeze with KDE 4.4.5. Basically, I can use my password for things like logging in, or authenticating on a shell with sudo successfully. But in other cases, I am asked to "become root", and when I enter my usual password, I'm told to check if I entered my password correctly. This happens with Aptitude (terminal GUI), for example: from Actions, I try to update the package list, and when I enter my password, I can read su: Authentication failure. However, if I start Aptitude by typing kdesudo aptitude on Konsole I can enter my password in the authentication box successfully, and use Aptitude with administrative privileges.
The example is valid also for other applications, such as System Monitor: just for the sake of the example, if I try to stop a process owned by root, say Aptitude, I'm asked for a password to become root, but my password doesn't do the trick. I'll have to open it from terminal with kdesudo ksysguard, then I'll be allowed to kill that process. Does it have anything to do with my choice at installation? I think I must have chosen to leave the root password field blank, and only entered my password as a user, for it explained I could become root anytime if there was need to with sudo.
I have a system running with few users and servers (apache/mysql/postfix). After extracting one tar archive in '/home' none of my users are being able to access their home directory. Even other system users (like www-data/mysql) are also not being able to access any directory. Only root can access the system. I have checked file permissions, many files/directories are set to 777 rest are 755.
View 5 Replies View Relatedhow to install rpm as non-root user
View 5 Replies View RelatedDebian 8/Cinnamon fresh install. /home is being shared with two other OS's, Mint and openSUSE. At the login screen I enter my user name and password and the screen blacks for 1-2 seconds and comes back asking for user name and password. I can login as root. As root I can launch the Group & Users GUI and attempt to set the user's password, and pressing the 'change' button does nothing obvious.
I can set the user's password in a terminal, which reports success. I tried to switch users and login with the changed password and I get the same failure. If I try to login with the original password I get an incorrect password error, suggesting that the password is being processed properly and the problem is elsewhere.
On previous installs with Mate and the default desktop (Gnome) I didn't have this problem. So, the questions are: Is it Cinnamon? Is it an unlucky chance bad install? Config files are typically in /home, which is being shared with Mate and KDE, is this the problem?
on my netbook I've tried to make possible for my user to shutdown without needing a password. battery could run low when I'm not in front of it. Editing sudoers has allowed my user to shutdown the system, but Gnome still prompts me for the root password whenever root is logged in too. That's usually the case, because to avoid entering the root password multiple times whenever I need elevated privileges and not wanting to cache the root password, I keep a Root Terminal always open.
View 6 Replies View RelatedAfter a week of working with Debian, I decided to install the KDE3 version straight from an NetInstall CD. This fixed some issues for me as well as made networking and folder sharring a snap! But now its time to add all the extra packages I need.
Here's the problem: Using any kind of Package Manager yields the same results:
E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (var/lib/dpkg/), in another process using it?
RESULT=100
I've tried apt-get from root command line and the KPackage Manager that comes with KDE3 with same results. I have only one user that was created during Debian install. I'm having some other problems, from what I've seen on the net, they all seem to point to not having proper Super User access (I'm guessing here). What could cause this error? AND/OR How do I make sure I have top level access to the configure the system? (I tried logging in as "root", but the login errored out saying that this was not allowed).
Why can't you use the command "sudo su root" from a user besides Ubuntu?
View 2 Replies View RelatedI have installed OpenSUSE a few months ago and worked fine. But from yesterday i can't login with root user. I received the message:
Login: root
Invalid user name
I have no question for password neither.
I use a SLES-machine (should be similar to opensuse I guess) and ad AIX-machine and got the following error:
Every time a none-root user runs an "at"-command on the linux machine, there is an error written into the errorreport of the AIX-machine. the error is the following: <82>Jul 12 22:32:09 linux-hostname atd[10754]: PAM audit_log_user_message() failed: Operation not permitted
I already checked the files /etc/at.deny (exists with users listed like "alias, backup, bin, ..." but not the user that causes the error-message) and /etc/at.allow (which does not exist but is not necessary, as far as I could read from the internet).
Suddenly Debian started rejecting my user pw and I have to login as root. Perhaps this is a coincidence, but this started when I re-booted after adding Russian keyboard layout in etc/default/keyboard. The Russian keyboard added successfully.
Being logged in as root, renewed the pw of my user account (actually assigned the same as wes previously), got confirmation the the pw has been changed. Reloaded. Yet it keeps complaining that the pw is wrong.
I'm using Debian Jessie Cinnamon right now. I've got 1 user account on my machine--fred--as well as root, of course. "fred" is an administrator, and many times that is enough for root priviledges, for example, I can install packages via apt or dpkg. However, I cannot access "Users and Groups", or install packages via GDebi, with my password. For that, I have to have the root password.
I know that it is possible to let the admin account handle everything and not even need root--for example, Mint and (I believe) Ubuntu do it this way. I don't know how, though.
Code: Select allgroups fred
fred : fred cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner bluetooth
I did disable the root account by Code: Select allsudo passwd -l root to see if it would make any change. Nothing different happened except that I now can't use GDebi or access "Users and Groups" since the root account and therefore password is inactivated. Not a big deal to get it back, though.
I have lost my password for my root and for my user account.
Code: Select alluser@debian:~$ su
Password:
su: Authentication failure
user@debian:~$ su
Password:
su: Authentication failure
user@debian:~$ su
I have just installed a gust debian 8 on debian 8 host in virtualbox, and when i wonted too login as su/root on the host there where no login possible, is there a way to regain the root password for the host?
I have a very strange problem.ometimes, yes sometimes not all the time, I get a Destination Host Unreachable when I ping a computer on my network. If I switch to root using su I can ping that same computer. Here is a screen shot:
joseph@laptop:~$ ping 192.168.1.14
PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data.
From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
[code]...
I upgraded a Guruplug Display machine running Lenny to Squeeze. It's running Linux on a MicroSD device, running an ARM-cpu.
# uname -a
Linux gplugD 2.6.29 #1 Wed Feb 16 17:59:04 IST 2011 armv5tejl GNU/Linux
yeri@gplugD ~ $ cat /etc/debian_version
6.0.1
However, after rebooting, every non root user was unable to access anything related to the net.This means, DHCP failed to auto start, ntp is giving errors, etc
# ntpq -p
localhost: timed out, nothing received
***Request timed out
daemon.log:
Mar 27 06:07:44 localhost ntpd[1478]: ./../lib/isc/unix/ifiter_ioctl.c:348: unexpected error:
Mar 27 06:07:44 localhost ntpd[1478]: making interface scan socket: Permission denied
Mar 27 06:07:44 localhost ntpd[1478]: Too many errors. Shutting up.
As root:
gplugD ~ # ping 85.12.6.171 -c 1
PING 85.12.6.171 (85.12.6.171) 56(84) bytes of data.
64 bytes from 85.12.6.171: icmp_req=1 ttl=58 time=42.1 ms
[code]....
I installed Jessie with Cinnamon alongside Win 7 - all went quite well though I did have to do a bit of guessing along the way.
Following online tutorials etc, I tried to install sudo from the terminal. It did not go well - some stuff appeared that was not shown in the instructions from many sites. So I abandoned it, or so I thought.
Then I discovered that my root password was no longer recognised. So I reset it, following online instructions.
This was successful apparently, as I can log in as root and see this in the terminal.
But on trying to start Synaptic ( and later others), I found that the new root password would is not authenticated, but my user password does authenticate successfully. This seems to be the wrong way round!
I am not sure if this is the correct forum to post this as I have usually been able to find the answers from other peoples threads.The error I receive is below.(changed "at" as can't post links)"#1045 - Access denied for user 'root' at 'localhost' (using password: NO)" Not entirely sure what has happened here. I have had this server running for a long time and today it seems to have spat it's dummy out!I have checked the config.inc.php and the controluser and controlpass are entered correctly so the error saying a password is not being usPHP Code:Thisis needed for cookie based authentication to encrypt password incookie
View 2 Replies View RelatedHow can I enable "Auto Login" for root user?In " Yast --> Security And Users --> User And Group Management --> Expert options --> Login Settings " is just my own user and there's no root user to choose.
View 9 Replies View Related