04-01-2002
No problem with Aqua!
No, no, no--no problem with Aqua at all. Acrobat 5.0 was a Classic application, meaning its code hadn't had the ~10% rewrite necessary to run natively in both OS 9.x and OS X, meaning that its component files hadn't been given UNIX permissions. The owner of those files was "System," but since I couldn't remove them from the trash (except, as I later discovered) to their original location, I couldn't get to them because each username has its own Trash, and I couldn't find the one that had the files when I logged in as the superuser (this is a failing on my part).
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I write a sh script that zip and copy to tape all files that older then 2 hours.
1. The way I choose is - touch a file with "now - 2 hours", then use fine with '! -newer'
2. Do you have any other idea to do it ?
tnx. (1 Reply)
Discussion started by: yairon
1 Replies
2. Programming
I need to compile a file,but 'make' does
not work.please tell me how to use it or
need which tools? (3 Replies)
Discussion started by: dsun5
3 Replies
3. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
4. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
5. Email Antispam Techniques and Email Filtering
Here is a crude procmail recipe that I quickly created (NOT a procmail recipe expert, btw) that has been catching lots of spam (current second after the charset_spam recipe posted earlier):
:0B
* .*If.you.do.not.wish.to.receive...*
more_spam
:0B
* You.requested.to.receive.this.mailing... (0 Replies)
Discussion started by: Neo
0 Replies
6. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
7. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
8. Linux
Hello
i am trying to empty the trash using rm or rmdir command . Any idea how to delete the folders and subfolders using one of the above commands?
Thank You (2 Replies)
Discussion started by: exhumation
2 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
A set of Linux shell scripts is required to allow users to ‘remove' files without them really disappearing... (1 Reply)
Discussion started by: mr100perecent
1 Replies
LEARN ABOUT DEBIAN
logprn
logprn(1) logtools logprn(1)
NAME
logprn - merge Common-Log Format web logs based on time-stamps
SYNOPSIS
logprn logfile idle-time[:max-wait] command
DESCRIPTION
The logprn program is designed to print new data that is appended to log files. It will wait until a specified amount of time has elapsed
since the last write to the file before printing the data. It will print the data by pipeing it to a specified command. The command will
be run by popen(3) so the usual shell commands will operate (whether this is a bug or a feature is a matter of opinion).
OPTIONS
logfile
specifies a file to read data from. It should be a regular file not a pipe, device, or anything else.
idle-time
max-wait
command
EXIT STATUS
0 Never happens, this program will run forever.
1 Bad command-line parameters or couldn't stat the log file on startup - couldn't start the program.
2 File disappeared or became unreadable at run-time.
3 Can't run the specified command.
AUTHOR
This program, its manual page, and the Debian package were written by Russell Coker <russell@coker.com.au>.
BUGS
Uses popen (3) but I consider this a feature not a bug.
SEE ALSO
popen(3)
Russell Coker <russell@coker.com.au> 0.06 logprn(1)