What file needs to be modified so that Pulseaudio starts automatically when in the root account? Currently, it is necessary to start Pulseaudio from the "Run" dialog when in the root account. I recall there was a file that prevents Pulseaudio from being run as root and that particular line had to be deleted in order for it to work.
I prefer to run my computer from the root account. If not, do not preach about the "dangers" of running as root.
I've started to get emails that would typically come from [URL] as [URL]. These emails come from services that send out emails (backup programs) directly, or from cronjobs. I've logged in as the non-root account and either sudo su - or su - to root and the restart the service at one point or another. If I login directly as root and bounce the service or cron the emails come across as from root. I don't see anything in my environment variables after I su to indicate what would cause this. I'm not sure where else to look? A pam setting? This seems to have happened between Fedora 10 and 14 (did a bunch of overdue upgrades recently) I've only got Fedora so I don't have anything to compare to. In Fedora 10 I did not have this problem.
I am trying to log into a server with a particular account. Let's say I don't know the password for that account. Can I do this using ssh? I am wondering if it is possible to do it in one command, instead of logging in as root and running su.
I've had nothing but trouble with Pulseaudio in Fedora 14. I had managed to get rid of it in Fedora 10 with the command: su -c "yum remove alsa-plugins-pulseaudio pulseaudio" I just don't want to have to deal with Pulseaudio anymore. It does not like my sound card and gets in the way. Is there a Linux distribution that does not use Pulseaudio ?
I came to debian from fedora so there I used ( su - ) to become root user. So my question is that in debian, is it same using ( su ) and ( su - ) or here also using ( su - ) is preferred with slash or without slash. What is the correct and secure way in debian with full root status.
One more question relating gedit sources.list
I use as root account : gedit /etc/apt/sources.list (and then enter and sources file in gedit open)
Is this correct method or any other way as when save after changing entries inside it says error.
I try to use FTP to put new files and catalogs on my server and I always run into problems that I have not the right to create catalogs and files in the named catalogs and so on, it is very annoying.Is there a way around this problem or do I have to activate root account to not run into these problems all the time? I have worked with different UNIX-versions and variants for the last 15 years at least and have always had access to root account, why is it so dangerous to have access to root account in ubuntu?
I deleted the root line in passwd and shadow and then tried to copy the backup and was able to put it all back to normal from rescue mode. However when i get to my login screen i can not login as root anymore or even after logged in as another user i can not su - or su root, it tells me that root user does not exist......
I have set up my crontab and whilst Im logged in and it works (It runs my shell script), however when Im not logged in, the script does not run. Initially I set the time/date to 0 0 * * * (Midnight every day), as this did not work, I tested it with to 0 * * * * (every hour) whilst logged in and the script starts.
I use crontab -e to set it up under the root account..Im sure you dont have to be logged in for it to run?, but maybe im missing a step or just overdosing on Linux and need a holiday:-)
I want to add a new user. For that purposeI switch to su and give root passwd. There I gave a command " useradd ". [smith@localhost smith]#adduser when i press enter key by typing adduser command it say me "Command not found" .Then i log off from my own account and login again from root account. The command "useradd" is then accepted.is there any way that without logging off from normal user account I may enter my roor accout and work as a root account instead to log off from normal user account.
How do I activate networking? (I am currently logged in from Ubuntu on another computer). I installed Debian Squeeze on an iMac 7.1 (which works perfectly well with ubuntu) from the netinstall CD (today's daily build), and of course I deactivated root login, coming from ubuntu. Now I find I have to enter my root password (login password will not do) to activate networking! Is this a joke? I had the network configured with DHCP during install! So how do I activate the root account, or, more to the point, how do I get by in Debian without activating root login?
I have a dual-boot system with windows xp and suse 11.2. The last time tried to enter to suse i couldn't login to my account ,only as root. I tried to solve this through suse dvd repair option andit detected a problem in grub. i repaired it but still nothing.Also the /home partition exists and i can access it when i login as root.
A while back I don't know what I did but I messed up my root user account and now the password that I think is supposed to be for the account doesn't work anymore.In an attempt to fix it I rebooted and went into recovery mode and then edited the sudoers file. This appears to have been good enough to be me by but now I'm running into problems installing or changing configurations in gnome. For example, I just installed Asterisk via the terminal the other day and had no problems because I could use sudo. But just now I tried installing Gastman via the Ubuntu Software Center and of course it asked for the root password.I entered my usual root password when I use sudo and it doesn't work.
I then went to the terminal and entered sudo apt-get install gastman and it worked fine becuase I used my sudo password for my account. So it seems I can do things just fine via the terminal but when in gnome it doesn't work. I went into the Users and Groups section in Gnome to attempt to set or change the root password but of course I have to unlock the application which requires the root password.
I've got an old computer around that I've put Ubuntu server 8.04 on.At the moment, this is only a little hobby of mine purely for educational purposes. (Great for learning Linux!) After using this tutorial:URL...for setting up a LAMP-server, I'm trying to figure out is whether or not setting up a root-password is necessary or not. I think the tutorial is really great for a newbie, but it consistently uses su instead of sudo.I'm aware of the fact that setting a root-password isn't recommended in the documentation, but don't you need a root-account to be able to run tools such as webmin?
I first started using Ubuntu and I liked the sudo facility because I didn't need to remember two passwords, so when I installed Debian I wrote the same password for the limited and the root account. Is this very bad for security? I mean can a program started from my regular account immediately become root or something?
a user called, cannot login - forgot the password - common case ( 200 user system )- but this one seems to be a bit different:
user tries to log in via ssh - login/passwd incorrect, via telnet - no problem
tried a few different users on ssh - no problem... It seems the access denied applies to just a single, standard user account - only via ssh, all other users are able to login... tried also to change the passwd, no difference. beside re-creating the account, can you think about anything else? system: RHEL AS3, 2.4.21-51ELsmp
I am an experienced Linux user, but have never used Salix before. I have a root account set up on my other Linux distros, but can not figure it out using Salix. The reason I want a root account in Salix because I believe in freedom of choice, and my choice always was and always will be to have a root account set up so I can login as root. I am aware of the risk involed in creating a root account.
I have Centos installed as part of Strongbolt on a Cobalt RAQ550 Machine. The Admin password and the root password is supposed to be identical. However, I can only login as admin. If I try to access using root, the SSH session shuts down. If I enter another passowrd it gives the correct response and says incorrect password. If I login as admin and then try SU Root - It displays a list of commmand options for SSH and does not allow me to login.
I just installed Debian 6 on a server and when the server powers up, it shows me all the accounts I created in order for me to choose and login under an account, except for the root account. At the colo where the server is going, they need the root account at the login screen.