03-04-2011
/ tells it to go all the way to the root of the disk. You'd have to type the whole thing:
/System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background ...which actually would work, if you wanted to make it all on one line. You wouldn't even need to CD that way, I think.
You need ./ because the shell doesn't run things in the current directory. You have to tell it 'in the current directory' explicitly. This is a security feature (so someone can't drop files in your directory and have you unknowingly run them.)
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
(SuSE Linux 8.2 Personal)
I'm sure the answer to this will be simple, but it's been driving me insane for the last couple days.
SuSE 8.2 comes with a bunch of screensavers, but a handful of them just repeatedly display 'sh: line 1: fortune: command not found'. I've been scouring endlessly... (4 Replies)
Discussion started by: Darkstripes
4 Replies
2. Filesystems, Disks and Memory
i would like to create a screensaver for unix platform in java. with an interface through which i can change the kinds of *.jpg images that r being displayed and also the background music. i don't know how to go about it. can anyone help please :confused: (0 Replies)
Discussion started by: madatyou1
0 Replies
3. UNIX for Advanced & Expert Users
All XKCD jokes aside, can a feature be added to a bash script to move the mouse every X seconds to prevent the screensaver from activating? As is it, I launch mplayer through a script that sets some preferences (such as -zoom). Can I add something to that script which wiggles the mouse?
Relevant... (1 Reply)
Discussion started by: dotancohen
1 Replies
4. Linux
Hi!
First of all, let me warn you I'm quite new to the world of LINUX and Operating Systems understanding, so that's why I pose these newbie and stupid qustions...
Anyway, I'm trying to build my own simple shell in C and I'm getting some problems in implementing the background process ('&')... (10 Replies)
Discussion started by: neimaD
10 Replies
5. AIX
Guys,
We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem.
Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run.
... (2 Replies)
Discussion started by: anandsbr
2 Replies
6. Shell Programming and Scripting
Dear all,
I'm writing a KornShell script that calls inside it a function in background mode
#!/bin/ksh
function myfunction
{ . . .}
myfunction |&
. . .
How can I capture the PID of the function myfunction that runs in background?
Thanks in advance
:) (2 Replies)
Discussion started by: dariyoosh
2 Replies
7. Solaris
I have a Dell Vostro running Solaris 10 x86 and I am trying to get it to activate the screensaver when no one is logged it. However, the screensaver only seems to activate when someone logs in and then the computer locks. How would I go about fixing this problem? Any help yall can offer would be... (3 Replies)
Discussion started by: MajorJRO
3 Replies
lndir(1X) lndir(1X)
NAME
lndir - create a shadow directory of symbolic links to another directory tree
SYNOPSIS
lndir fromdir [todir]
DESCRIPTION
lndir makes a shadow copy todir of a directory tree fromdir, except that the shadow is not populated with real files but instead with sym-
bolic links pointing at the real files in the fromdir directory tree. This is usually useful for maintaining source code for different
machine architectures. You create a shadow directory containing links to the real source which you will have usually NFS mounted from a
machine of a different architecture, and then recompile it. The object files will be in the shadow directory, while the source files in
the shadow directory are just symlinks to the real files.
This has the advantage that if you update the source, you need not propagate the change to the other architectures by hand, since all
source in shadow directories are symlinks to the real thing: just cd to the shadow directory and recompile.
The todir argument is optional and defaults to the current directory. The fromdir argument may be relative (e.g., ../src) and is relative
to todir (not the current directory).
Note that RCS, SCCS, and CVS.adm directories are not shadowed.
Note also that if you add files, you must run lndir again. Deleting files is difficult because the symlinks will point to places that no
longer exist.
BUGS
The patch routine needs to be able to change the files. You should never run patch from a shadow directory.
Use a command like the following to clear out all files before you can relink (if the fromdir has been moved, for instance):
find todir -type l -print | xargs rm
The following command will find all files that are not directories:
find . ! -type d -print
lndir(1X)