: Or use multiple finds in logical locations spread over a day or two.
and Sean followed up,
Alternately, you could _prune_ some directories you know you shouldn't
Ah, but without shell access, how would I know what those directories
are -- either those to search per Gerald's advice or those to prune per
Sean's? FTR, the places make showed up were not under any of the three
directories in Gerald's example: it was at /usr/ccs/bin/make and
Bugger that, though I see as I'm finishing this message off, you've found
that the login and mail servers are running compatible OS' now...
Just to make something clear: my problem was not on Panix; I knew that
on Panix, which I'm posting from, the mail server and the shell servers
run the same OS. But the compatibility came as a surprise on the system
where I had the problem, because it wasn't the cae in the past. (The
shell server is running Sun_OS 5.9; the mail server is using 5.8.)
You could potentially invoke FTP or scp, or whatever, FROM the mail host
via a script to retrieve files from elsewhere.
Didn't need to. The mail server can see a cross-mount of my $HOME. It
can read my .procmailrc and my .forward, and it can store messages in
subdirectories of my $HOME.
Controlled invocation of emailed shell scripts?
The thing is, if you don't know what's in the universe, you don't know
what to try, and if you stumble on something to try and successfully
rule it out, you don't know what's left.
procmail mailing list