Re: Bug#1895: run-parts does not run scripts without #!/...

> 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]> <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> Absolu

Re: Bug#1895: run-parts does not run scripts without #!/...

Jeff Noxon spoke unto the world and said: >My plan is to rewrite run-parts in C or C++. However, I probably won't >have that done until next weekend. I've never done any perl programming Could I ask a favor that run-parts *skips* directories rather than reporting "component /etc/cron.*/RCS is no

Re: Bug#1895: run-parts does not run scripts without #!/...

Jeff Noxon writes: > My plan is to rewrite run-parts in C or C++. However, I probably won't > have that done until next weekend. I've never done any perl programming > before, so i'd like to avoid making changes to the perl script unless > you think this bug is urgent enough to warrant it. No, f

Re: Bug#1895: run-parts does not run scripts without #!/...

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

Bug#1895: run-parts does not run scripts without #!/...

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 t

Bug#1895: run-parts does not run scripts without #!/...

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, any

Re: Bug#1895: run-parts does not run scripts without #!/...

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

Bug#1895: run-parts does not run scripts without #!/...

Harald Schueler writes ("Bug#1895: run-parts does not run scripts without #!/..."): > 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, displa

Bug#1895: run-parts does not run scripts without #!/...

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