11-16-2001
Backslash is special to the shell. It quotes the next character. For example:
echo ;
will not work because the shell sees the semicolon as a separator and will not pass it to the echo command. So to echo a semicolon we need to do:
echo \;
But what if we wanted to echo a backslash? We then we need to do this:
echo \\
So your four backslashes are needed just to deliver two backslashes to the sed program.
But sed also uses the backslash specially. And so if you really want sed to use a backslash as an ordinary character, you need to feed sed a double backslash as well.
If it makes you feel any better, 8 backslashes is no record.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey,
This is probably going to sound like an immensely stupid and dull question, but can someone please tell me whether the forward slash on the web address (http://) signifies that it is running on UNIX?
hanks (1 Reply)
Discussion started by: steverocliffe
1 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone! :)
I've been asked to write an article breaking down the basics of UNIX password information etc., and I've come across something in which I cannot find a definition for within Google.
Very simply, can anyone tell me what the difference is between a standard UNIX password, and... (4 Replies)
Discussion started by: hellz
4 Replies
3. UNIX for Dummies Questions & Answers
when I execute a command in like "run.sh," I can run it two ways:
./run.sh
or
. run.sh
What is the difference? (1 Reply)
Discussion started by: DarkLord
1 Replies
4. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
I have standard web server log file. It contains different columns (like IP address, request result code, request type etc) including a date column with the format .
I have developed a log analysis command line utility that displays... (1 Reply)
Discussion started by: TariqYousaf
1 Replies
5. Shell Programming and Scripting
My script is as follows:
#!/bin/bash
STR1="test"
echo $STR1
STR2="/bldtmp/"$STR1
echo $STR2
STR3=$STR2'/tmp'
echo $STR3
output i am geting
----------------
test
/bldtmp/test
/tmptmp/test
but my need is:
------------------
test
/bldtmp/test (1 Reply)
Discussion started by: dchoudhury
1 Replies
6. Cybersecurity
When I try to access my website's Administrator page (mysite.com/administrator), I'm redirected to (mysite.comadministrator), as if the slash was removed from the URL
The funny thing is that I can access it if I enter 2 slashes (mysite.com//administrator)
Any ideas of what might be causing it? (4 Replies)
Discussion started by: rlopes
4 Replies
7. Shell Programming and Scripting
I have got the following contents and please can you advise me on how to extract the following data that appears between the very first slashes.
Thanks
i.e 576 , 10000, 1299
3/576/GPP///////NONE/0
50/10000/GPP///D4////GPP/0
234/1299/GPP///////NONE/0 (3 Replies)
Discussion started by: Sudhakar333
3 Replies
8. Programming
I want to print 4052 slashes using this C program.
#include <stdio.h>
void main()
{
int i;
for (i=0; i<4052; i++)
printf ("/");
}
When i compile this via gcc am getting this error :
http://gyazo.com/e0403e4789575d181d1695f9db3e6d6e.png
Can anyone point out what am doing wrong? (15 Replies)
Discussion started by: vish6251
15 Replies
9. Shell Programming and Scripting
So I'm trying to pass certain json elements as env vars and use them later on in a script.
Sample json:
JSON='{
"Element1": "file-123456",
"Element2": "Name, of, company written in, a very weird way",
"Element3": "path/to/some/file.txt",
}'
(part of the) script:
for s... (5 Replies)
Discussion started by: da1
5 Replies
10. UNIX for Beginners Questions & Answers
In Bash shell - the ps -ef shows only the /bin/bash but the script name is not displayed ? Is there any way to get the script names for the process command ?
--- Post updated at 08:39 AM ---
in KSH (Korn Shell), my command output shows the script names but when run in the Bash Shell... (3 Replies)
Discussion started by: i4ismail
3 Replies
LEARN ABOUT DEBIAN
syslogout
SYSLOGOUT(8) System Manager's Manual SYSLOGOUT(8)
NAME
syslogout - modular centralized shell logout mechanism
DESCRIPTION
syslogout is a generic approach to enable centralized shell logout actions for all users of a given system in a modular and centralized way
mostly aimed at avoiding work for lazy sysadmins. It has only been tested to work with the bash shell.
It basically consists of the small /etc/syslogout shell script which invokes other small shell scripts having a .bash suffix which are con-
tained in the /etc/syslogout.d/ directory. The system administrator can drop in any script he wants without any naming convention other
than that the scripts need to have a .bash suffix to enable automagic sourcing by the /etc/syslogout script.
For shell sessions, the contents of /etc/syslogout.d/" will be sourced by every user at logout if the following lines are present in his
$HOME/.bash_logout:
if [ -f /etc/syslogout ]; then
. /etc/syslogout
fi
If used for X sessions it is advisable to include the former statement into the Xreset script of the X display manager instead to prevent
that closing of an terminal emulator window yields unexpected results in your running X session if your X11 terminal emulator is using a
login shell. Be sure then to run it under the user-id of the X session's user. See the example files in /usr/share/doc/syslogout/ for
illustration.
Users not wanting /etc/syslogout to be sourced for their environment can easily disable it's automatic mechanism. It can be disabled by
simply creating an empty file called $HOME/.nosyslogout in the user's home directory using e.g. the touch(1) command.
Any single configuration file in /etc/syslogout.d/ can simply be overridden by any user by creating a private $HOME/.syslogout.d/ directory
which may contain a user's own version of any configuration file to be sourced instead of the system default. It's names have just to
match exactly the system's default /etc/syslogout.d/ configuration files. Empty versions of these files contained in the $HOME/.syslo-
gout.d/ directory automatically disable sourcing of the system wide version.
Naturally, users can add and include their own private scripts to be automagically executed by /etc/syslogout at logout time.
OPTIONS
There are no options other than those dictated by shell conventions. Anything is defined within the configuration scripts themselves.
SEE ALSO
The README files and configuration examples contained in /usr/share/doc/syslogout/ and the manual page for bash(1), xdm(1x),
xdm.options(5), and wdm(1x). Recommended further reading is everything related with shell programming.
If you need a similar mechanism for executing code at login time check out the related package sysprofile(8) which is a very close compan-
ion to syslogout.
BUGS
syslogout in its current form is mainly restricted to bash(1) syntax. In fact it is actually a rather embarrassing quick and dirty hack
than anything else - but it works. It serves the practical need to enable a centralized bash configuration until something better
becomes available. Your constructive criticism in making this into something better" is very welcome. Before i forget to mention it: we
take patches... ;-)
AUTHOR
syslogout was developed by Paul Seelig <pseelig@debian.org> specifically for the Debian GNU/Linux system. Feel free to port it to and use
it anywhere else under the conditions of either the GNU public license or the BSD license or both. Better yet, please help to make it into
something more worthwhile than it currently is.
SYSLOGOUT(8)