But if that loop ever stops running, the 'file' will block.
Ah, effectively a "replinishing" pipe. That would work. The downside, as you mentioned, is that it must be supported by a running process.
It would be nice to have a native file type (again, like an SQL view) that contains "instructions" to materialize data, but only materializes such data when it is read.
I am trying to add a permanent route on my server, but whenever i reboot it dissapears.
Please does anyone know the correct command to use.
route add XXX.XXX.XXX.XXX DDD.DDD.DDD.DDD
the above is what i have done.
ednut:)
using IRIX SGI software. (2 Replies)
On AIX 5.2 as root, installed Seamonkey and have to type
#/seakey/seamonkey/seamonkey to get it to run, which it does okay.
To set up a permanent alias, I did the following
(1) In a text editor
alias seamk='/seakey/seamonkey/seamonkey'
and saved it to /home/alias_file
(2) In a text editor... (7 Replies)
Hi guys,
I'm running Solars 8 on a V100 server at home for testing.
If I switch user to root and do:
# echo $PATH
This is the output:
/usr/sbin:/usr/bin
I'm using rsync over ssh and need to add /usr/local/bin and /user/local/sbin.
I do this by running the line:
#... (3 Replies)
I set my TERM variable to work with SMIT and everything works fine but when I logged out and log in again I have to set the variable again.
How can I set a permanent variable into the system so it will be as I wish even if a reboot is needed?
I set variables this way:
export VAR=value (7 Replies)
I have a file that reads File (X.txt)
Contents of record 1:
rdrDESTINATION_ADDRESS (String) "91 971502573813"
rdrDESTINATION_IMSI (String) "000000000000000"
rdrORIGINATING_ADDRESS (String) "d0 movies"
rdrORIGINATING_IMSI (String) "000000000000000"
rdrTRAFFIC_EVENT_TIME... (0 Replies)
I read this article as a way to do a non-permanent of something.
I saw 2 problems. The first that my rm is located at /bin/rm. I would assume I would change the location to /bin/rm. The second my rm is a executable file and not a text file. So will replacing my rm file with the shellscript... (3 Replies)
I try to understand the meaning of an inode. I wonder whether
an inode is unique (I'm pretty sure it is) and
whether it remains the same inode regardless of whatever happens to the file, dir or whatever?
I read somewhere that an inode stores info about the file, size... so changing the... (4 Replies)
See attached video for a demo on how to move back and forth from the desktop view to the mobile view.
Currently this only works for the home page, but I will work on some new PHP code in the future to make this work with the page we are currently on.
Edit: The issue with making every page ... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS --debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)