search for: shebang

...nary and locally compiled plugin. Note this does not go through valgrinding when you run ‘make check-valgrind’ so that needs to be fixed at some point in the future. Thanks: François Revol and Eric Blake. See also: https://www.redhat.com/archives/libguestfs/2018-November/msg00126.html --- tests/shebang.pl | 2 +- tests/shebang.py | 2 +- tests/shebang.rb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/shebang.pl b/tests/shebang.pl index 17c7821..e6f1630 100755 --- a/tests/shebang.pl +++ b/tests/shebang.pl @@ -1,4 +1,4 @@ -#!../nbdkit perl +#!../src/nbdkit ../plugins/p...

On 11/13/18 7:40 AM, Richard W.M. Jones wrote: >> (I think the error message is "incorrect ELF header") could be >> something to do with the way we use shebangs (#!). IIRC this also >> fails on FreeBSD so probably nbdkit is doing something which is not >> correct POSIX. > POSIX says that #! shebangs are undefined behavior. You're at the mercy of each operating system, because there is no portable solution across all systems. >...

On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: > if you leave it out the script will run in whatever environment it > currently is in. I'm reasonably certain that a script with no shebang will run with /bin/sh. I interpret your statement to mean that if a user is using ksh and enters the path to such a script, it would also run in ksh. That would only be true if you "sourced" the script from your shell.

...[Temporary directory for large files]) would be enough for now? Finally about the list of failing tests: https://pastebin.com/1PFG85DS Mostly these are because of the old qemu-io binary. The qemu-io -f option was added 4 years ago :-/ so it could be time to upgrade. This error: ./test-shebang-perl.sh: PID file was not created rect ELF header FAIL test-shebang-perl.sh (exit status: 1) (I think the error message is "incorrect ELF header") could be something to do with the way we use shebangs (#!). IIRC this also fails on FreeBSD so probably nbdkit is doing something which...

...now be at least compatible with both python2 (py2) and python3 (py3), some of them already are already py3 only. The build system still depends on Python in a few place, but it explicitly mentions Python3_EXECUTABLE, and the main dependency (llvm-build) is currently being removed in D89142. The shebangs have already been harmonized in D83857: some mention /usr/bin/env python, some mention /usr/bin/env python3, and none mention python2 anymore. It would be great to have all script use the same shebang, PEP394 [1] makes it (relatively) clear that in our case, explicitly requiring python3 is the way...

...related side topic: in your recent addition of eval.sh, you > wondered if we should promote it to a full-blown plugin rather than > just an example script. But reading 'man nbdkit-sh-plugin', there > is no mention of turning an executable script into a full-blown > plugin via a shebang, the way that python documents it. [I guess > 'man nbdkit' sort of mentions it under Shebang scripts] I believe it's not possible to do it for sh plugins. For (eg) python plugins it works like this: #!/usr/sbin/nbdkit python -> runs nbdkit python <script name> -&gt...

All, I have a script that runs script/runner via the shebang mechanism at the top o the file, like so: #!/usr/bin/env ./script/runner This works fine in development, how would I get it to run in non-development environments? Thanks, Wes -- Posted via http://www.ruby-forum.com/.

...ion of eval.sh, you > > > wondered if we should promote it to a full-blown plugin rather than > > > just an example script. But reading 'man nbdkit-sh-plugin', there > > > is no mention of turning an executable script into a full-blown > > > plugin via a shebang, the way that python documents it. [I guess > > > 'man nbdkit' sort of mentions it under Shebang scripts] > > > > I believe it's not possible to do it for sh plugins. > > > > For (eg) python plugins it works like this: > > > > #!/usr/sbin/...

...in your recent addition of eval.sh, you > > wondered if we should promote it to a full-blown plugin rather than > > just an example script. But reading 'man nbdkit-sh-plugin', there > > is no mention of turning an executable script into a full-blown > > plugin via a shebang, the way that python documents it. [I guess > > 'man nbdkit' sort of mentions it under Shebang scripts] > > I believe it's not possible to do it for sh plugins. > > For (eg) python plugins it works like this: > > #!/usr/sbin/nbdkit python > -> runs nbd...

...ffset2.sh | 2 +- tests/test-parallel-file.sh | 2 +- tests/test-parallel-nbd.sh | 2 +- tests/test-pattern-largest.sh | 2 +- tests/test-pattern.sh | 2 +- tests/test-python-exception.sh | 2 +- tests/test-random-sock.sh | 2 +- tests/test-shebang-perl.sh | 2 +- tests/test-shebang-python.sh | 2 +- tests/test-shebang-ruby.sh | 2 +- tests/test-single.sh | 2 +- tests/test-start.sh | 2 +- tests/test-tls-psk.sh | 2 +- tests/test-tls.sh | 2 +- tests/test-trunca...

On 04/24/2015 09:59 AM, Steve Lindemann wrote: > > A script with no shebang will run in the environment of the account > running the script. Bad test on my part, apparently. $ python >>> import os >>> os.execv('/home/gmessmer/test', ('test',)) Traceback (most recent call last): File "<stdin>", line 1, in <modul...

...strano to deploy, and found a few issues: 1) I must chmod 755 dispatch.cgi each time I deploy 2) script/parse/reaper also doesn''t have the executable attributes so the deployment fails. 3) database.yml as checked out from svn isn''t correct. Also, a few scripts get generated with shebang lines like #!c:\ruby\... Which later have to be changed. Anyone solved this? If so, how? Thanks. Regards, Rich

...> > > > wondered if we should promote it to a full-blown plugin rather than > > > > just an example script. But reading 'man nbdkit-sh-plugin', there > > > > is no mention of turning an executable script into a full-blown > > > > plugin via a shebang, the way that python documents it. [I guess > > > > 'man nbdkit' sort of mentions it under Shebang scripts] > > > > > > I believe it's not possible to do it for sh plugins. > > > > > > For (eg) python plugins it works like this: > >...

Dear R-devel, Recently I ran into trouble installing two separate packages, nloptr and ncdf4, both due to the same issue: they have scripts that have the shebang `#! /bin/sh', but have bashisms in them, i.e. non-POSIX-compliant bash scripts. I use dash [1] as my shell environment, since it's about 4x as fast as bash. It looks like it's recently also become the default shell for Debian (and thus Ubuntu). It took quite a while to figure out what...

...n R Pierce wrote: > On 4/24/2015 9:47 AM, Gordon Messmer wrote: >> On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: >>> if you leave it out the script will run in whatever environment it >>> currently is in. >> >> I'm reasonably certain that a script with no shebang will run with >> /bin/sh. I interpret your statement to mean that if a user is using >> ksh and enters the path to such a script, it would also run in ksh. >> That would only be true if you "sourced" the script from your shell. > > oh fun, just did some tests (usi...

...ous" > nature of it I still am wary of underestimating the cruftiness of the > buildbots, so I'll probably do it some time at night when the bots are > mostly green so that I can easily see if any bots *are* broken by this. While at it, can you call "env python2" in the shebang line? It makes it a lot easier for Python3 systems, like Arch. cheers, --renato

I just setup switchtower and I am very happy with it. Just one thing is giving me some headache: My development machine is windows and my deployment host is Unix. Each time I deploy I need to make dispatch.fcgi executable. I wrote my own task for that. But does there exist any smarter way to get this automated ? I think Subversion offers some possiblity to declare a file as executable, but no idea

...ion(): > + return 2 > + > +(where 2 is the latest version at the time this documentation was > +written). All newly written Python modules must have this function. > + > =head2 Executable script > > If you want you can make the script executable and include a "shebang" > @@ -120,6 +133,10 @@ nbdkit-plugin(3). Unrelated side topic: in your recent addition of eval.sh, you wondered if we should promote it to a full-blown plugin rather than just an example script. But reading 'man nbdkit-sh-plugin', there is no mention of turning an executable s...

What do you think about adding a shebang line to the samples so they can be launched on linux/mac like you can on windows? Roy

Please forgive my ignorance but I need a explanation of how to accomplish the following since I cannot figure it out from the documents. I have a Ruby script with a shebang line that looks like this: #!/usr/bin/env ruby On one particular host I have two Ruby interpreters installed; one the CentOS base version 1.8.6 in /usr/bin/ruby the other version 1.8.7 in /usr/local/bin/ruby. In my shell the which command finds /usr/local/bin/ruby. In a cron job the /usr/bin/ru...