Could I ask a favor that run-parts *skips* directories rather than
reporting component /etc/cron.*/RCS is not an executable plain file.
It's annoying that way...
Thanks,
Darren
[EMAIL PROTECTED] http://www.daft.com/~torin/[EMAIL PROTECTED]
[EMAIL PROTECTED]
Absolutely.
Jeff
On Sat, 25 Nov 1995, Ian Jackson wrote:
Run-parts does not run scripts not beginning with #!/... This may not be
a bug, but it should be documented. run-parts --test, however, displays
_all_ scripts, which is rather confusing, and not a test at all.
It does run them - or try to, anyway.
Harald Schueler writes (Re: Bug#1895: run-parts does not run scripts without
#!/...):
What it does is documented: It calls execvp, which in turn executes only
script _with_ #!/interpreter (or binaries of course).
Yes, I'm aware that execvp only runs scripts that are in the proper
executable
Ian Jackson writes:
The whole design of system() in Perl isn't conducive to good
error-trapping. I suppose it might be better to use fork oneself.
Jeff (you're the maintainer of this package, aren't you?) - would you
like me to send you an update that uses fork directly and produces an
I think I am going to rewrite run-parts in C. I don't know perl and don't
have the time to learn it just to fix run-parts. :)
Jeff
Harald Schueler writes (Bug#1895: run-parts does not run scripts without
#!/...):
Package: miscutils
Version: 1.3-5
Run-parts does not run scripts
Package: miscutils
Version: 1.3-5
Run-parts does not run scripts not beginning with #!/... This may not be
a bug, but it should be documented. run-parts --test, however, displays
_all_ scripts, which is rather confusing, and not a test at all.
Harald Schueler
Universitaet Essen
6 matches
Mail list logo
