Cant Get Netscape to work... I get this messsage:
Perhaps there is a problem with your name server? if your site must use a non-root name server, you will need to set the $SOCKS_NS environment variable to point at the appropreate name server. It may (or may not) be necessary to set this... (2 Replies)
i have this script i wrote, it chokes when running the add install client commandit keeps telling me the add_install_client command is incorrect.
When I put the print statement in front of the command so it will echo it, the command looks right on the screen. Yes im am an ametuer, im trying to... (2 Replies)
I am trying to do a head on a mainframe file and on doing ti just gives me a blank screen with nothing on it.
however, when i do a tail for the same file...i get a few lines on the screen.
i know tht mainframe files have all the records on one line...does this have to do something with this.... (10 Replies)
Hey guys i'm creating a dos style rename script, so if a user types say q14.* as the 1st param and b14.* as the 2nd and will rename all q14 files to b14 but keep the extensions, so i've developed nearly the full script "i think", if i use echo(echo "if $1 had been renamed it would now be... (3 Replies)
just downloaded Ajaxterm-0.10 on my Mac 10.5.8 and after a ./ajaxterm.py i get:
AjaxTerm at http://localhost:8022/
which looks ok but as soon i go to the website:
./ajaxterm.py:418: DeprecationWarning: 'I' format requires 0 <= number <= 4294967295
fcntl.ioctl(fd,... (0 Replies)
For some reason when I run these separately they work but when they are in a script file the second wont:
printf "%s\n" "$RANDOM"."$RANDOM" "$RANDOM"."$RANDOM" "$RANDOM"."$RANDOM" "$RANDOM"."$RANDOM" | tee $HOME/bpl/random
RANDOM1=$( <$HOME/bpl/random ) Anyone know why? (8 Replies)
This is my first script and I wont get it working.. sorry for being a total noob but here it is:
#./bin/sh -x
echo "1:st argument = $1";
echo "2:nd argument = $2";
grep "$1" "$2"
In the terminal I write, for example, su.sh sausage sausage.txt
Also tried su.sh "sausage" "sausage.txt" but... (2 Replies)
I just installed a fork of opensolaris, and I really like it.
I would hate going back to Ubuntu, But one issue, I cannot get my Dell Wireless 1450 Wireless USB Adapter working.
On Ubuntu 10.4 I just installed nonfree firmware, but I guess it doesn't work that way on Solaris, any help would be... (5 Replies)
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Hi,
I have setup my .profile with some helpful aliases and some set commands in it.
I have it as:
alias gr='autorep -G'
alias c='clear'
alias x='exit'
alias wcl='wc -l'
alias l1='ls -1 "$@"'
alias ll='ls -l "$@"'
alias la='ls -altr "$@"'
alias l='ls -ltr "$@"'
alias ml='m_ls -ltr... (5 Replies)
Discussion started by: grep_me
5 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)