10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i did a mistake. :(
user1 ]$ vi ~/.bashrc
sudo su - user2
now , whenever I try to login to user1 , it will login to user2.
How can I resolve this ? :rolleyes:
N.B
-- I do not have root access.
-- I dont know password of user2
-- this is a virtual machine. (1 Reply)
Discussion started by: linuxadmin
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I have file with 200K Records and each line with 400 character. I need to edit the some part of the file.
For example, i need to edit character from 115 to 125, 135to 145 and 344 to 361
Can you please anyone help me to do this?
Regards, (1 Reply)
Discussion started by: balasubramani04
1 Replies
3. Shell Programming and Scripting
I am writing a BASH script to update a webserver and then restart Apache. It looks basically like this:
#!/bin/bash
rsync /path/on/local/machine/ foo.com:path/on/remote/machine/
ssh foo.com sudo /etc/init.d/apache2 reloadrsync and ssh don't prompt for a password, because I have DSA encryption... (9 Replies)
Discussion started by: fluoborate
9 Replies
4. Shell Programming and Scripting
looking for a script or command to push out from a centralized machine to multiple machines. I have the software in place that will do this already, but I need to tell it what command to run on each machine with this file.
what I need is a script or command to edit a file in a specific manner.... (13 Replies)
Discussion started by: skunky
13 Replies
5. Shell Programming and Scripting
I have a file containing dates like below
2010 1 02
2010 2 01
2010 3 05
i want the dates to be like below
20100102
20100201
20100305
i tired using
awk '{printf "%s%02s%02s",$1,$2,$3}'
But it does not work,it puts all the dates in one line,i want them in seperate lines like the... (6 Replies)
Discussion started by: tomjones
6 Replies
6. Shell Programming and Scripting
I have a requirement, which is as follows
*. Folder contains list of xmls. Script has to create new xml files by copying the existing one and renaming it by appending "_pre.xml" at the end.
*. Each file has multiple <Name>fileName</Name> entry. The script has to find the first occurance of... (1 Reply)
Discussion started by: sudesh.ach
1 Replies
7. Shell Programming and Scripting
I have a file oratab with entry like this
SCADAG:/esitst1/oracle/product/9.2.0.8:Y
I am trying to discover a way to change the 9.2.0.8 part of this to something like 10.2.0.4 as part of an upgrade script.
I have tried
cat /etc/oratab >>/tmp/oratab... (1 Reply)
Discussion started by: sewood
1 Replies
8. UNIX for Dummies Questions & Answers
Hello Everyone
I am new to this forum.
I am having a requirement to edit the file(the file is having some sql code).
And this file is in my colleagues login. This is readonly
Now I would like to edit this file.
In which way can I do this? (1 Reply)
Discussion started by: pradkumar
1 Replies
9. Shell Programming and Scripting
Hi,
Could anyone give me a idea how to strip the lines from a given file. example
***********
1st occurence
1st occurence
1st occurence
1st occurence
***********
2nd occurence
2nd occurence
2nd occurence
2nd occurence
2nd occurence
2nd occurence
*************
3rd occurence
3rd... (10 Replies)
Discussion started by: sentak
10 Replies
10. UNIX for Dummies Questions & Answers
ok I have a list of files for example:
130-4-32.HindIII.0.ids
130-4-32.HindIII.0.ppm
130-4-32.HindIII.0.ppm.gz
130-4-33.HindIII.0.bands
130-4-33.HindIII.0.ics
130-4-33.HindIII.0.ids
130-4-33.HindIII.0.ppm
130-4-33.HindIII.0.ppm.gz
130-4-34.HindIII.0.bands ... (1 Reply)
Discussion started by: lorcet222
1 Replies
VISUDO(8) MAINTENANCE COMMANDS VISUDO(8)
NAME
visudo - edit the sudoers file
SYNOPSIS
visudo [-c] [-q] [-s] [-V] [-f sudoers]
DESCRIPTION
visudo edits the sudoers file in a safe fashion, analogous to vipw(8). visudo locks the sudoers file against multiple simultaneous edits,
provides basic sanity checks, and checks for parse errors. If the sudoers file is currently being edited you will receive a message to try
again later.
There is a hard-coded list of one or more editors that visudo will use set at compile-time that may be overridden via the editor sudoers
Default variable. This list defaults to "/usr/bin/editor". Normally, visudo does not honor the VISUAL or EDITOR environment variables
unless they contain an editor in the aforementioned editors list. However, if visudo is configured with the --with-env-editor option or
the env_editor Default variable is set in sudoers, visudo will use any the editor defines by VISUAL or EDITOR. Note that this can be a
security hole since it allows the user to execute any program they wish simply by setting VISUAL or EDITOR.
visudo parses the sudoers file after the edit and will not save the changes if there is a syntax error. Upon finding an error, visudo will
print a message stating the line number(s) where the error occurred and the user will receive the "What now?" prompt. At this point the
user may enter "e" to re-edit the sudoers file, "x" to exit without saving the changes, or "Q" to quit and save changes. The "Q" option
should be used with extreme care because if visudo believes there to be a parse error, so will sudo and no one will be able to sudo again
until the error is fixed. If "e" is typed to edit the sudoers file after a parse error has been detected, the cursor will be placed on
the line where the error occurred (if the editor supports this feature).
OPTIONS
visudo accepts the following command line options:
-c Enable check-only mode. The existing sudoers file will be checked for syntax and a message will be printed to the standard
output detailing the status of sudoers. If the syntax check completes successfully, visudo will exit with a value of 0. If a
syntax error is encountered, visudo will exit with a value of 1.
-f sudoers Specify and alternate sudoers file location. With this option visudo will edit (or check) the sudoers file of your choice,
instead of the default, /etc/sudoers. The lock file used is the specified sudoers file with ".tmp" appended to it.
-q Enable quiet mode. In this mode details about syntax errors are not printed. This option is only useful when combined with
the -c option.
-s Enable strict checking of the sudoers file. If an alias is used before it is defined, visudo will consider this a parse error.
Note that it is not possible to differentiate between an alias and a host name or user name that consists solely of uppercase
letters, digits, and the underscore ('_') character.
-V The -V (version) option causes visudo to print its version number and exit.
ENVIRONMENT
The following environment variables may be consulted depending on the value of the editor and env_editor sudoers variables:
VISUAL Invoked by visudo as the editor to use
EDITOR Used by visudo if VISUAL is not set
FILES
/etc/sudoers List of who can run what
/etc/sudoers.tmp Lock file for visudo
DIAGNOSTICS
sudoers file busy, try again later.
Someone else is currently editing the sudoers file.
/etc/sudoers.tmp: Permission denied
You didn't run visudo as root.
Can't find you in the passwd database
Your userid does not appear in the system passwd file.
Warning: {User,Runas,Host,Cmnd}_Alias referenced but not defined
Either you are trying to use an undeclare {User,Runas,Host,Cmnd}_Alias or you have a user or host name listed that consists solely of
uppercase letters, digits, and the underscore ('_') character. In the latter case, you can ignore the warnings (sudo will not
complain). In -s (strict) mode these are errors, not warnings.
Warning: unused {User,Runas,Host,Cmnd}_Alias
The specified {User,Runas,Host,Cmnd}_Alias was defined but never used. You may wish to comment out or remove the unused alias. In -s
(strict) mode this is an error, not a warning.
SEE ALSO
vi(1), sudoers(5), sudo(8), vipw(8)
AUTHOR
Many people have worked on sudo over the years; this version of visudo was written by:
Todd Miller
See the HISTORY file in the sudo distribution or visit http://www.sudo.ws/sudo/history.html for more details.
CAVEATS
There is no easy way to prevent a user from gaining a root shell if the editor used by visudo allows shell escapes.
BUGS
If you feel you have found a bug in visudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/
SUPPORT
Limited free support is available via the sudo-users mailing list, see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or
search the archives.
DISCLAIMER
visudo is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose are disclaimed. See the LICENSE file distributed with sudo or
http://www.sudo.ws/sudo/license.html for complete details.
1.7.4 July 14, 2010 VISUDO(8)