search for: runscript

...@ -56,7 +56,7 @@ class TestSuiteTest(FileBasedTest): >>>>>>> res = testscript.parse(test.getSourcePath()) >>>>>>> if litConfig.noExecute: >>>>>>> return lit.Test.Result(Test.PASS) >>>>>>> - runscript, verifyscript = res >>>>>>> + runscript, verifyscript, metricscripts = res >>>>>>> >>>>>>> # Apply the usual lit substitutions (%s, %S, %p, %T, >>>>>>> ...) >>>>>>> tmpDir...

...class TestSuiteTest(FileBasedTest): >>>>>>>> res = testscript.parse(test.getSourcePath()) >>>>>>>> if litConfig.noExecute: >>>>>>>> return lit.Test.Result(Test.PASS) >>>>>>>> - runscript, verifyscript = res >>>>>>>> + runscript, verifyscript, metricscripts = res >>>>>>>> >>>>>>>> # Apply the usual lit substitutions (%s, %S, %p, %T, >>>>>>>> ...) >>>>>>...

...Test(FileBasedTest): >>>>>>>>> res = testscript.parse(test.getSourcePath()) >>>>>>>>> if litConfig.noExecute: >>>>>>>>> return lit.Test.Result(Test.PASS) >>>>>>>>> - runscript, verifyscript = res >>>>>>>>> + runscript, verifyscript, metricscripts = res >>>>>>>>> >>>>>>>>> # Apply the usual lit substitutions (%s, %S, %p, %T, >>>>>>>>> ...) >>...

...tigation). Then >> run: >> >> ? system2('fmtutil-sys', '--all') >> ? # or tinytex:::fmtutil() if fmtutil-sys.exe is not on PATH >> >> and TeX Live would throw an error like this: >> >> ...\username\AppData\Roaming\TinyTeX\bin\windows\runscript.tlu:864: no >> appropriate script or program found: fmtuti~1 >> >> The command "fmtutil-sys" is longer than 8 characters and hence >> shortened to "fmtutil~1". Yes, in principle, TeX Live should work with >> short path names, but it doesn't at t...

...ytex() after you finish the investigation). Then > run: > > ? system2('fmtutil-sys', '--all') > ? # or tinytex:::fmtutil() if fmtutil-sys.exe is not on PATH > > and TeX Live would throw an error like this: > > ...\username\AppData\Roaming\TinyTeX\bin\windows\runscript.tlu:864: no > appropriate script or program found: fmtuti~1 > > The command "fmtutil-sys" is longer than 8 characters and hence > shortened to "fmtutil~1". Yes, in principle, TeX Live should work with > short path names, but it doesn't at the?moment. I have...

...: >>> >>> ?? system2('fmtutil-sys', '--all') >>> ?? # or tinytex:::fmtutil() if fmtutil-sys.exe is not on PATH >>> >>> and TeX Live would throw an error like this: >>> >>> ...\username\AppData\Roaming\TinyTeX\bin\windows\runscript.tlu:864: no >>> appropriate script or program found: fmtuti~1 >>> >>> The command "fmtutil-sys" is longer than 8 characters and hence >>> shortened to "fmtutil~1". Yes, in principle, TeX Live should work with >>> short path names, but...

...d cleanly via tinytex::uninstall_tinytex() after you finish the investigation). Then run: system2('fmtutil-sys', '--all') # or tinytex:::fmtutil() if fmtutil-sys.exe is not on PATH and TeX Live would throw an error like this: ...\username\AppData\Roaming\TinyTeX\bin\windows\runscript.tlu:864: no appropriate script or program found: fmtuti~1 The command "fmtutil-sys" is longer than 8 characters and hence shortened to "fmtutil~1". Yes, in principle, TeX Live should work with short path names, but it doesn't at the moment. I haven't figured out if it w...

...mon shorewall # /etc/init.d/shorewall start * Starting firewall... Warning: default route ignored on interface eth0 iptables: No chain/target/match by that name ERROR: Command "/sbin/iptables -t mangle -A outtos -p tcp -d 0.0.0.0/0 --dpor t ssh -j TOS --set-tos 16" Failed /sbin/runscript.sh: line 532: 14701 Terminated /sbin/shorewall star t >/dev/null [ !! ] tos contains #SOURCE DEST PROTOCOL SOURCE PORTS DEST PORTS TOS all all tcp - ssh...

Hello ~ I am using the Capistrano recipe outlined in this post to restart my backgroundrb server: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000718.html My Version: ~~~~~~~~~~~~ task :before_restart, :roles => :app do restart_backgroundrb end task :start_backgroundrb, :roles => :app do sudo "nohup

...using for root is what's in openldap (and is different from the root account in /etc/passwd). There's always another error message in my logs with each attempt, but I have no idea where it's coming from, and I don't know if it has anything to do with anything: rc-scripts: /sbin/runscript.sh: must be root to run init scripts If I create the machine account with `smbldap-useradd -w' (to try to join the machine in two steps like can be done in a Windows-only environment), I get errors in the log about not being able to access the ldap directory unless root. The stupid part is...

Exactly where does R search for foo.R if I type source("foo.R")? Only from current working directory (same as getwd()), from all directories specified by e.g. $PATH? Thanks. Daehyok Shin

Exactly where does R search for foo.R if I type source("foo.R")? Only from current working directory (same as getwd()), from all directories specified by e.g. $PATH? Thanks. Daehyok Shin

...virtio-blk? Multiqueue is not supported > by QEMU but it's already supported by Linux (commit 6a27b656fc). I expect performance would be better. Seems google cloud VM uses both nvme and virtio-scsi. Not sure if virtio-blk is also used. https://cloud.google.com/compute/docs/disks/local-ssd#runscript > > To me, the advantage of nvme is that it provides more than decent performance on > unmodified Windows guests, and thanks to your vendor extension can be used > on Linux as well with speeds comparable to virtio-blk. So it's potentially > a very good choice for a cloud provi...

...manifested when I was testing some scripts using '-aHPv' as the default options. Test machines: slackware 8.1 & 9.1, stock build chain for each. (I hope I gave enough info.. not exactly clear headed at the moment) -- Registered Linux User Number 140066 http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=140066 "Failure is not an option. (It comes bundled with Windows.)" "If it ain't broke, overclock it."

Hi all: logrotate is broken on my stock 4.1 install. After hunting and hunting I found there is a bug filed with Redhat on the issue. logrotate fails becasue my /tmp partition is mounted noexec. I understand it is that way for security reasons. The box in question is on a dedicated hosting site and that's the way it was handed off to me, built. Some said setting TMPDIR=/var/tmp;export

Using dovecot-1.0-rc19 (quotas are working good, btw) on Gentoo, I have a strange problem. On boot, dovecot doesn't start, the init script just times out. From the command line, it starts instantly without problem. Also, using a program called 'monit' to make sure processes stay running and restart them if they stop, if I manually stop dovecot, it is then unable to start it (calling

On 10/30/23 17:18, Yihui Xie wrote: > Hi, > > It may have been so for 20+ years but I just discovered today that system() > would always try to use the short path of a command on Windows: > https://github.com/wch/r-source/blob/635a67/src/gnuwin32/run.c#L141 If > that's true, I wonder if it could provide an option to disable this > behavior, because we recently ran into a

...:07 orig+owner.group -rw-r--r-- 5 erik users 395 2004-09-14 17:07 orig+time (The 5th link being the hash file itself) My question is simple enough. Are there plans to make --link-by-hash pay attention to file externals? Erik -- Registered Linux User Number 140066 http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=140066 "Failure is not an option. (It comes bundled with Windows.)" "If it ain't broke, overclock it."

...init script... Here is what you said (this is from the skype chat): [2012-06-04 10:40:43 AM] timosirainen: probably put to dovecot init script or something I guess I could manually modify my init script, but I'm clueless as to where.how. The current (gentoo) init script is: > #!/sbin/runscript > # Copyright 1999-2012 Gentoo Foundation > # Distributed under the terms of the GNU General Public License, v2 or > later > # $Header: > /var/cvsroot/gentoo-x86/net-mail/dovecot/files/dovecot.init-r4,v 1.1 > 2012/12/01 10:40:49 eras Exp $ > > extra_started_commands=&quot...

I'm getting this message in my logwatch email notification: --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present sdb:<3>Buffer I/O error on device sdb, l ...: 2 Time(s) Buffer I/O error on device sdb, l ...: 12 Time(s) hde: dma_intr: error=0x84 { DriveStat ...: 12 Time(s) hde: dma_intr: status=0x51 { DriveReady