Re: Script typeface.

pe...@easthope.ca wrote: > From: debian-u...@howorth.org.uk > Date: Wed, 30 Oct 2024 22:06:02 + > > Have you looked at https://elementor.com/blog/handwriting-fonts/ ? > > Looked since you mentioned. The heading I cited appears to be > in Pacifico font. > > Elementor is charging us

Re: Script typeface.

From: debian-u...@howorth.org.uk Date: Wed, 30 Oct 2024 22:06:02 + > Have you looked at https://elementor.com/blog/handwriting-fonts/ ? Looked since you mentioned. The heading I cited appears to be in Pacifico font. Elementor is charging us 50+ dollars/yr. I don't see a mention of

Re: Script typeface.

From: Ash Joubert Date: Thu, 31 Oct 2024 12:26:39 +1300 > Try filtering Google Fonts by Calligraphy / > Handwritten. That gives 81 fonts to consider. Good, thx, ... P. -- VoIP: +1 604 670 0140 work: https://en.wikibooks.org/wiki/User:Pet

Re: Script typeface.

pe...@easthope.ca wrote: > Hi, > > Apparently the page here was constructed using something called > Elementor. https://www.friendsofthegulfislands.ca > > The heading is in a script style of typeface. > > I'm interested to find a free, open source replacment font. Not > necessarily the same i

Re: script/history

On Mon 05/02/2024 at 00:45, Greg Wooledge wrote: ... > If you're one of these "I want every command I ever run to be in my > shell history, retained forever, and I don't care how much space it > takes" people, then there are web pages out there that can help you. > I don't follow that philosophy m

Re: script/history

(Re)posting the below as requested, and can confirm history -r seems to have the desired effect. Thanks. - Original message - From: Will Mengarini To: Gareth Evans Cc: debian-user@lists.debian.org Subject: Re: script/history Date: Monday, 5 February 2024 01:02 * Gareth Evans [24

Re: script/history

* Gareth Evans [24-02/04=Su 09:46 +]: > Re the script command, does anyone know of a way to make > commands run during a script session appear in bash history too? You want the 'history -r' command, "explained" by `help history`. After you end the script, you're back in the bash instance you

Re: script/history

On Mon, Feb 05, 2024 at 12:28:38AM +, Gareth Evans wrote: > I was trying to view the history of commands run during a script session. > > user@qwerty:~$ script foo > Script started, output log file is 'foo'. > user@qwerty:~$ date > Mon 5 Feb 00:21:16 GMT 2024 > user@qwerty:~$ exit > exit > Sc

Re: script/history

On Sun 04/02/2024 at 19:45, David Wright wrote: ... > According to this man page for csh (but includes tcsh): > > https://linux.die.net/man/1/csh > > the "a" that modifies modifiers is a "[feature] of tcsh not found > in most csh(1) implementations (specifically, the 4.4BSD csh)". It > appears t

Re: script/history

On Sun 04/02/2024 at 17:33, Greg Wooledge wrote: ... > The script(1) utility has NOTHING to do with running ordinary shell > scripts. I understand that. I was trying to view the history of commands run during a script session. user@qwerty:~$ script foo Script started, output log file is 'foo'.

Re: script/history

On Sun, Feb 04, 2024 at 01:45:27PM -0600, David Wright wrote: > SCRIPT(1) User Commands SCRIPT(1) > [ … ] > HISTORY >The script command appeared in 3.0BSD. > > I have no idea why "the history mechanism" is even mentioned > in the man page for script. It appear

Re: script/history

On Sun 04 Feb 2024 at 16:01:29 (+), Gareth Evans wrote: > On Sun 04/02/2024 at 13:24, Max Nikulin wrote: > > On 04/02/2024 16:46, Gareth Evans wrote: > >> Re the script command, does anyone know of a way [ … ] > > [...] > >> man script says > >> > >> "SEE ALSO > >> csh(1) (for the his

Re: script/history

On Sun, Feb 04, 2024 at 04:01:29PM +, Gareth Evans wrote: > It seemed to me initially (as I should perhaps have stated) that man script > was suggesting that csh was a component or depedency (of script), which > seemed to be contradicted by it not being installed. On reflection, > possibly,

Re: script/history

On Sun 04/02/2024 at 13:24, Max Nikulin wrote: > On 04/02/2024 16:46, Gareth Evans wrote: >> Re the script command, does anyone know of a way to make commands run during >> a script session appear in bash history too? > [...] >> man script says >> >> "SEE ALSO >> csh(1) (for the history

Re: script/history

Oh you're right, I entirely overlooked the usage of 'script' and didn't understand the question right, sorry. On Sun, 2024-02-04 at 06:28 -0500, Michael Grant wrote: > > $ script foo.txt > > Script started, output log file is 'foo.txt'. > > $ date > > Sun 4 Feb 09:44:00 GMT 2024 > > $ exit > > ex

Re: script/history

On 04/02/2024 16:46, Gareth Evans wrote: Re the script command, does anyone know of a way to make commands run during a script session appear in bash history too? [...] man script says "SEE ALSO csh(1) (for the history mechanism)" but $ man csh No manual entry for csh echo $SH

Re: script/history

On Sun, Feb 04, 2024 at 09:46:09AM +, Gareth Evans wrote: > man script says > > "SEE ALSO >csh(1) (for the history mechanism)" > > but > > $ man csh > No manual entry for csh I'm so glad that we're entering an era where it's normal *not* to have csh installed and used. That shell

Re: script/history

> $ script foo.txt > Script started, output log file is 'foo.txt'. > $ date > Sun 4 Feb 09:44:00 GMT 2024 > $ exit > exit > Script done. > $ history|tail -n2 > 30797 2024-02-04 09:43:57 script foo.txt > 30798 2024-02-04 09:44:21 history|tail -n2 > > I did try to search on this but just got lo

Re: script/history

On Sun, 2024-02-04 at 09:46 +, Gareth Evans wrote: > Re the script command, does anyone know of a way to make commands > run during a script session appear in bash history too? Maybe this: https://serverfault.com/questions/16204/how-to-make-bash-scripts-print-out-every-command-before-it-execut

Re: Script does not do what it is told to do

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2019-10-26 9:55 p.m., The Wanderer wrote: > On 2019-10-26 at 21:33, Ken Heard wrote: > >> The tar scripts now look like this. >> --- >> #!/bin/bash # Script to back up all browser files in direc

Re: Script does not do what it is told to do

On 2019-10-26 at 21:33, Ken Heard wrote: > The tar scripts now look like this. > --- > #!/bin/bash > # Script to back up all browser files in directory /home/ken/mozilla. > echo here > tar -cpzf /media/fde/backups/kbrowsers.tgz --exclude-caches

Re: Script does not do what it is told to do

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I want at this time to thank all of you for taking the time to provide various suggestions as to how to fix the problems I describe in my original post and in my previous thread 'Signs of hard drive failure?' My reason for the thank you is that early M

Re: Script does not do what it is told to do

Ken Heard writes: > Whenever I run this script -- or several others like it > > #!/bin/bash > # Script to back up all browser files in directory /home/ken/mozilla. > STARTDIR=$PWD > cd /home/ken > tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ > --wildcards -T docs/tarlists/kbrowse

Re: Script does not do what it is told to do

On 25/10/2019 16:37, David Wright wrote: On Fri 25 Oct 2019 at 14:28:02 (+0100), Michael Howard wrote: On 25/10/2019 14:11, Greg Wooledge wrote: On Fri, Oct 25, 2019 at 08:33:09AM +0100, Michael Howard wrote: On 24/10/2019 23:37, Ken Heard wrote: #!/bin/bash # Script to back up all browser fi

Re: Script does not do what it is told to do

On Fri 25 Oct 2019 at 11:49:46 (-0400), The Wanderer wrote: > On 2019-10-25 at 11:37, David Wright wrote: > > On Fri 25 Oct 2019 at 14:28:02 (+0100), Michael Howard wrote: > >> On 25/10/2019 14:11, Greg Wooledge wrote: > > >>> Untrue. I pointed out the flaws last time this subject was > >>> discu

Re: Script does not do what it is told to do

On 2019-10-25 at 11:37, David Wright wrote: > On Fri 25 Oct 2019 at 14:28:02 (+0100), Michael Howard wrote: > >> On 25/10/2019 14:11, Greg Wooledge wrote: >>> Untrue. I pointed out the flaws last time this subject was >>> discussed on this mailing list. Was that just a few days ago, or >>> was

Re: Script does not do what it is told to do

On Fri 25 Oct 2019 at 14:28:02 (+0100), Michael Howard wrote: > On 25/10/2019 14:11, Greg Wooledge wrote: > > On Fri, Oct 25, 2019 at 08:33:09AM +0100, Michael Howard wrote: > > > On 24/10/2019 23:37, Ken Heard wrote: > > > > #!/bin/bash > > > > # Script to back up all browser files in directory /h

Re: Script does not do what it is told to do

On Fri 25 Oct 2019 at 03:45:45 (+0200), deloptes wrote: > Ken Heard wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On 2019-10-24 7:12 p.m., Anuradha Weeraman wrote: > > > >> On Thu, Oct 24, 2019 at 06:37:08PM -0400, Ken Heard wrote: > >>> tar -czf /media/fde/backups/kbrow

Re: Script does not do what it is told to do

Hi, Ken Heard wrote: > Whenever I run this script -- or several others like it > [...] > tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ > - --wildcards -T docs/tarlists/kbrowsers.lst > [...] > it returns the following: > [...] > tar (child): /media/ssda/backups/kbrowsers.tgz: Cannot

Re: Script does not do what it is told to do

On Fri, Oct 25, 2019 at 02:28:02PM +0100, Michael Howard wrote: > On 25/10/2019 14:11, Greg Wooledge wrote: > > On Fri, Oct 25, 2019 at 08:33:09AM +0100, Michael Howard wrote: > > > On 24/10/2019 23:37, Ken Heard wrote: > > > > #!/bin/bash > > > > # Script to back up all browser files in directory

Re: Script does not do what it is told to do

On 25/10/2019 14:11, Greg Wooledge wrote: On Fri, Oct 25, 2019 at 08:33:09AM +0100, Michael Howard wrote: On 24/10/2019 23:37, Ken Heard wrote: #!/bin/bash # Script to back up all browser files in directory /home/ken/mozilla. STARTDIR=$PWD cd /home/ken tar -czf /media/fde/backups/kbrowsers.tgz

Re: Script does not do what it is told to do

On Fri, Oct 25, 2019 at 08:33:09AM +0100, Michael Howard wrote: > On 24/10/2019 23:37, Ken Heard wrote: > > #!/bin/bash > > # Script to back up all browser files in directory /home/ken/mozilla. > > STARTDIR=$PWD > > cd /home/ken > > tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ > >

Re: Script does not do what it is told to do

On Fri, Oct 25, 2019 at 09:33:51AM +0200, john doe wrote: > On 10/25/2019 9:16 AM, to...@tuxteam.de wrote: > > On Fri, Oct 25, 2019 at 02:40:00AM +0200, deloptes wrote: > >> Ken Heard wrote: > >> > >>> Whenever I run this script -- or several others like it > >>> > >>> #!/bin/bash > >>> # Script to

Re: Script does not do what it is told to do

On 10/25/2019 9:16 AM, to...@tuxteam.de wrote: > On Fri, Oct 25, 2019 at 02:40:00AM +0200, deloptes wrote: >> Ken Heard wrote: >> >>> Whenever I run this script -- or several others like it >>> >>> #!/bin/bash >>> # Script to back up all browser files in directory /home/ken/mozilla. >>> STARTDIR=$P

Re: Script does not do what it is told to do

On 24/10/2019 23:37, Ken Heard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Whenever I run this script -- or several others like it #!/bin/bash # Script to back up all browser files in directory /home/ken/mozilla. STARTDIR=$PWD cd /home/ken tar -czf /media/fde/backups/kbrowsers.tgz --e

Re: Script does not do what it is told to do

Ken Heard wrote: > the archive.  It is properly mounted, and I can write files to it and > read those files.  As I said in my original post I am able to write > the archive successfully to /media/fde/backups/ by copying the tar > command line to a console and read the contents of the tarball. >

Re: Script does not do what it is told to do

On Fri, Oct 25, 2019 at 02:40:00AM +0200, deloptes wrote: > Ken Heard wrote: > > > Whenever I run this script -- or several others like it > > > > #!/bin/bash > > # Script to back up all browser files in directory /home/ken/mozilla. > > STARTDIR=$PWD > > cd /home/ken > > tar -czf /media/fde/backu

Re: Script does not do what it is told to do

On 2019-10-24 at 18:37, Ken Heard wrote: > Whenever I run this script -- or several others like it > it returns the following: > > ken@Turing:~$ tarkbrowsers > tar (child): /media/ssda/backups/kbrowsers.tgz: Cannot open: No such > file or directory How are you invoking the script? What does

Re: Script does not do what it is told to do

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2019-10-24 8:40 p.m., deloptes wrote: > Ken Heard wrote: > >> Whenever I run this script -- or several others like it >> >> #!/bin/bash # Script to back up all browser files in directory >> /home/ken/mozilla. STARTDIR=$PWD cd /home/ken tar -czf >>

Re: Script does not do what it is told to do

Ken Heard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 2019-10-24 7:12 p.m., Anuradha Weeraman wrote: > >> On Thu, Oct 24, 2019 at 06:37:08PM -0400, Ken Heard wrote: >>> tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ - >>> --wildcards -T docs/tarlists/kbrowsers.

Re: Script does not do what it is told to do

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2019-10-24 7:12 p.m., Anuradha Weeraman wrote: > On Thu, Oct 24, 2019 at 06:37:08PM -0400, Ken Heard wrote: >> tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ - >> --wildcards -T docs/tarlists/kbrowsers.lst > > Try removing the singl

Re: Script does not do what it is told to do

Ken Heard wrote: > Whenever I run this script -- or several others like it > > #!/bin/bash > # Script to back up all browser files in directory /home/ken/mozilla. > STARTDIR=$PWD > cd /home/ken > tar -czf /media/fde/backups/kbrowsers.tgz  --exclude-caches \ > --wildcards -T docs/tarlists/kbrowser

Re: Script does not do what it is told to do

On Thu, Oct 24, 2019 at 06:37:08PM -0400, Ken Heard wrote: > tar -czf /media/fde/backups/kbrowsers.tgz --exclude-caches \ > - --wildcards -T docs/tarlists/kbrowsers.lst Try removing the single '-' at the beginning of the second line... -- Regards Anuradha

Re: script purge-old-kernels

On Wed, Feb 15, 2017 at 03:30:55PM +, Wolfgang Truber wrote: Hello, why is under Debian no possibility to install the script purge-old-kernels or the package bikeshed (this package includes the script purge-old-kernels). There appears to be a program called "purge-old-kernels" in the byo

Re: script purge-old-kernels

On Wed, 15 Feb 2017 15:30:55 + Wolfgang Truber wrote: Hello Wolfgang, >why is under Debian no possibility to install the script >purge-old-kernels or the package bikeshed (this package includes the >script purge-old-kernels). bikeshed seems to have been superseded by byobu. That package co

Re: Script vs command line behaviour

On Sat, 15 Oct 2016, Andre Majorel wrote: > Or is pkill more than a wrapper around kill(pid, 15) and > kill(pid, 9) ? pkill is quite less prone to killing the wrong process due to a race when you use it properly. In the general case one should avoid SIGKILL. Trying other signals that allow for o

Re: Script vs command line behaviour

On 2016-10-12 08:40 -0400, Greg Wooledge wrote: > On Wed, Oct 12, 2016 at 09:34:22PM +0900, Mark Fletcher wrote: > > # The systemctl stop for svnserve may not work as I haven't got around to > > # making a stop script for it. > > # So kill the process the old fashioned way > > ps -ef | grep svnser

Re: Script vs command line behaviour

On Thu, 13 Oct 2016, Mark Fletcher wrote: > but I don't completely understand what you mean. Are you saying that, > even though the command to start fetchmail is not an invokation of a > systemd unit, the fact that it is happening from inside a script that is > run by a systemd unit somehow allo

Re: Script vs command line behaviour

On Thu, Oct 13, 2016 at 04:55:06PM +0200, Nicolas George wrote: > Le duodi 22 vendémiaire, an CCXXV, Mark Fletcher a écrit : > > > strace -f -e execve -s 1 -o /tmp/my_script.$$.$(date +%Y%m%d%H%M%S) & > > > But there is no my_script. in /tmp... WhaFu? > > My bad, I forgot the end of the comma

Re: Script vs command line behaviour

Le duodi 22 vendémiaire, an CCXXV, Mark Fletcher a écrit : > > strace -f -e execve -s 1 -o /tmp/my_script.$$.$(date +%Y%m%d%H%M%S) & > But there is no my_script. in /tmp... WhaFu? My bad, I forgot the end of the command: -p $$ (insert just before the final ampersand) Command explained: st

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 05:17:20PM +0200, Nicolas George wrote: > You can debug what happens to your script by adding this line near the > beginning: > > strace -f -e execve -s 1 -o /tmp/my_script.$$.$(date +%Y%m%d%H%M%S) & > > Tomorrow, the file in /tmp will tell you what happened. > OK I

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 04:29:01PM +0200, Nicolas George wrote: > Le primidi 21 vendémiaire, an CCXXV, Mark Fletcher a écrit : > > Fetchmail isn't set up as a service through systemd, although mysql and > > svnserve are. fetchmail is just started from this script (or supposed to > > be!) and laun

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 05:59:10PM +0200, Frank wrote: > Op 12-10-16 om 17:17 schreef Mark Fletcher: > >I wonder if passing the --fetchmailrc option will work. The systemd > >journal snippet I included in my original post shows that fetchmail is > >getting started successfully -- but by the morning

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 04:51:40PM -0400, Jude DaShiell wrote: > ># and restart the services we stopped > >systemctl start svnserve > >systemctl start mysql > >sudo -u mark fetchmail -d 900 > > > I think the issue revolves around unknown pwd. Perhaps running fetchmail as > the user rather than ro

Re: Script vs command line behaviour

On Wed, 12 Oct 2016, Mark Fletcher wrote: Date: Wed, 12 Oct 2016 08:34:22 From: Mark Fletcher To: debian-user@lists.debian.org Subject: Script vs command line behaviour Resent-Date: Wed, 12 Oct 2016 12:34:43 + (UTC) Resent-From: debian-user@lists.debian.org Greetings I am observing a stra

Re: Script vs command line behaviour

Op 12-10-16 om 17:17 schreef Mark Fletcher: I wonder if passing the --fetchmailrc option will work. The systemd journal snippet I included in my original post shows that fetchmail is getting started successfully -- but by the morning it's not running. Now, clearly nothing gets past me, but that m

Re: Script vs command line behaviour

Le duodi 22 vendémiaire, an CCXXV, Mark Fletcher a écrit : > You bring up a good point, actually. I'm calling systemctl stop and > systemctl start to stop and start mysql -- and I'm doing that in a > script that is itself being called by a systemd unit (the one triggered > by the timer). I wonde

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 10:36:40AM -0400, Gene Heskett wrote: > On Wednesday 12 October 2016 09:40:57 Mark Fletcher wrote: > > > On Wed, Oct 12, 2016 at 08:40:12AM -0400, Greg Wooledge wrote: > > > On Wed, Oct 12, 2016 at 09:34:22PM +0900, Mark Fletcher wrote: > > > > # The systemctl stop for svns

Re: Script vs command line behaviour

On Thu, Oct 13, 2016 at 12:09:12AM +0900, Mark Fletcher wrote: On Wed, Oct 12, 2016 at 04:29:01PM +0200, Nicolas George wrote: Le primidi 21 vendémiaire, an CCXXV, Mark Fletcher a écrit : > Fetchmail isn't set up as a service through systemd, although mysql and > svnserve are. fetchmail is just

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 04:29:01PM +0200, Nicolas George wrote: > Le primidi 21 vendémiaire, an CCXXV, Mark Fletcher a écrit : > > Fetchmail isn't set up as a service through systemd, although mysql and > > svnserve are. fetchmail is just started from this script (or supposed to > > be!) and laun

Re: Script vs command line behaviour

On Wednesday 12 October 2016 09:40:57 Mark Fletcher wrote: > On Wed, Oct 12, 2016 at 08:40:12AM -0400, Greg Wooledge wrote: > > On Wed, Oct 12, 2016 at 09:34:22PM +0900, Mark Fletcher wrote: > > > # The systemctl stop for svnserve may not work as I haven't got > > > around to # making a stop scrip

Re: Script vs command line behaviour

Le primidi 21 vendémiaire, an CCXXV, Mark Fletcher a écrit : > Fetchmail isn't set up as a service through systemd, although mysql and > svnserve are. fetchmail is just started from this script (or supposed to > be!) and launched by hand from the command line when that fails. > > So at least sys

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 09:56:06AM -0400, Greg Wooledge wrote: > On Wed, Oct 12, 2016 at 10:40:57PM +0900, Mark Fletcher wrote: > > ...Any thoughts on what is preventing the restart of fetchmail from > > working? > > Nothing in particular. I haven't used fetchmail in many years, and > never as a

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 08:40:12AM -0400, Greg Wooledge wrote: > On Wed, Oct 12, 2016 at 09:34:22PM +0900, Mark Fletcher wrote: > > # The systemctl stop for svnserve may not work as I haven't got around to > > # making a stop script for it. > > # So kill the process the old fashioned way > > ps -e

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 10:40:57PM +0900, Mark Fletcher wrote: > ...Any thoughts on what is preventing the restart of fetchmail from > working? Nothing in particular. I haven't used fetchmail in many years, and never as a "service" at the system level. So, just general thoughts: 1) Use "system

Re: Script vs command line behaviour

On Wednesday 12 October 2016 08:40:12 Greg Wooledge wrote: > And stop using -9 (SIGKILL). Forever. Pretend it never existed. That's a bit harsh. The tool exists for a good reason :-) "Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever

Re: Script vs command line behaviour

On Wed, Oct 12, 2016 at 09:34:22PM +0900, Mark Fletcher wrote: > # The systemctl stop for svnserve may not work as I haven't got around to > # making a stop script for it. > # So kill the process the old fashioned way > ps -ef | grep svnserve | grep -v grep | awk '{print $2}' | xargs kill -9 Plea

Re: Script doesn't work when it is run using '#!/bin/sh'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Apr 16, 2016 at 03:47:24PM +0100, Aero Maxx wrote: > On 16/04/2016 14:08, to...@tuxteam.de wrote: > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA1 > > > >On Sat, Apr 16, 2016 at 01:22:09PM +0100, Aero Maxx wrote: > >>I have a number of bash

Re: Script doesn't work when it is run using '#!/bin/sh'

On Saturday 16 April 2016 16:30:19 Jeremy Nicoll wrote: > On Sat, 16 Apr 2016, at 16:33, Gene Heskett wrote: > > And I still miss ARexx. > > Even bash cannot do the intimate to the os things that ARexx could > > do. > > Have you considered using Regina REXX or ooREXX instead? Yes, but typically b

Re: Script doesn't work when it is run using '#!/bin/sh'

On Sat, 16 Apr 2016, at 16:33, Gene Heskett wrote: > And I still miss ARexx. > Even bash cannot do the intimate to the os things that ARexx could do. Have you considered using Regina REXX or ooREXX instead? -- Jeremy Nicoll - my opinions are my own.

Re: Script doesn't work when it is run using '#!/bin/sh'

On Saturday 16 April 2016 10:47:24 Aero Maxx wrote: > On 16/04/2016 14:08, to...@tuxteam.de wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Sat, Apr 16, 2016 at 01:22:09PM +0100, Aero Maxx wrote: > >> I have a number of bash scripts that work perfectly fine on fedora > >> 2

Re: Script doesn't work when it is run using '#!/bin/sh'

On 16/04/2016 14:08, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Apr 16, 2016 at 01:22:09PM +0100, Aero Maxx wrote: I have a number of bash scripts that work perfectly fine on fedora 23, but do not work on debian 8. I've tried to sort it out myself, but am a l

Re: Script doesn't work when it is run using '#!/bin/sh'

Hi, Aero Maxx wrote: > >wordpress_beta.sh: 8: bashtest.sh: [[: not found If it is called "bashtest.sh" then it is plausible that it wants to be run by bash. Obviously it expects /bin/sh to be bash. to...@tuxteam.de wrote: > try running the script with "bash

Re: Script doesn't work when it is run using '#!/bin/sh'

On Sat 16 Apr 2016 at 15:08:58 (+0200), to...@tuxteam.de wrote: > On Sat, Apr 16, 2016 at 01:22:09PM +0100, Aero Maxx wrote: > > I have a number of bash scripts that work perfectly fine on fedora > > 23, but do not work on debian 8. I've tried to sort it out myself, > > but am a little stuck now h

Re: Script doesn't work when it is run using '#!/bin/sh'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Apr 16, 2016 at 01:22:09PM +0100, Aero Maxx wrote: > I have a number of bash scripts that work perfectly fine on fedora > 23, but do not work on debian 8. I've tried to sort it out myself, > but am a little stuck now hopefully someone is able

Re: (script) Re: Rediscovering a forgotten command

David Wright wrote: Quoting Richard Owlett (rowl...@cloud85.net): A few months ago I came across a command which would save all keyboard input to the current console and all output displayed on that console. That information would be saved to a default file or to a user specified file. IIRC the

Re: Script to email details not working in cron

Sven Hartge wrote: > You don't need the manually invoke /bin/bash if you just add > "#!/bin/bash" as the first line of your shell script, which Don already > pointed out: > >> 3) It may not be executable. Yes. Make sure it is executable. chmod a+x /home/user/bin/email-script Bob P.S. Persona

Re: Script to email details not working in cron

Manikandan M wrote: > I couldn't find why the script is not working in cron. Just replaced the > crontab entry with the following and it worked > * 9 * * * /bin/bash /user/bin/email-script This will run the script _every minute_ on the ninth hour. I don't think this is what you really want. It

Re: Script to email details not working in cron

Hi, I couldn't find why the script is not working in cron. Just replaced the crontab entry with the following and it worked * 9 * * * /bin/bash /user/bin/email-script Thanks everyone for your help. Regards, Mani On Fri, Jan 2, 2015 at 9:13 PM, Don Armstrong wrote: > On Fri, 02 Jan 2015, Ma

Re: Script to email details not working in cron

On Fri, 02 Jan 2015, Manikandan M wrote: > I have written a small script to email (using ssmpt) some details, and > scheduled it in crontab. The script is running as per time mentioned in the > cron but ssmtp is not sending the mail. please find the details below. > > user@host ~ $ cat bin/email-s

Re: Script to email details not working in cron

Manikandan M wrote: > I have written a small script to email (using ssmpt) some details, and > scheduled it in crontab. The script is running as per time mentioned in the > cron but ssmtp is not sending the mail. please find the details below. A couple of details to provide background to understan

Re: Script to email details not working in cron

On Fri, Jan 02, 2015 at 06:39:27PM +, Manikandan M wrote: Are other scripts running fine? Can you throw a silly date >>/tmp/imalive into it and see? Does ssmtp (I'm unfamilar with it) requies some special env-var that can be unset when running from Cron? -- People are like potatos. They d

Re: Script to email details not working in cron

Thanks for the quick response Patrick. I have given the full path for all the executables in the script. Still i'm not getting the email. The first line of the script works which updates the details-file. The third line of the script works which updates the status of the email operation. Both the d

Re: Script to email details not working in cron

On Fri, Jan 2, 2015 at 1:39 PM, Manikandan M wrote: > Hi, > > I have written a small script to email (using ssmpt) some details, and > scheduled it in crontab. The script is running as per time mentioned in the > cron but ssmtp is not sending the mail. please find the details below. > > user@host

Re: script line not working as its supposed to, but why?

On Wed, Dec 11, 2013 at 01:44:51PM +, Sharon Kimble wrote: > On Wed, 11 Dec 2013 12:42:51 +0100 > "Gian Uberto Lauri" wrote: > > > Sharon Kimble writes: > > > But there is no consistency with the creation date, the menu > > > itself is regenerated whenever I install a new programme, and the

Re: script line not working as its supposed to, but why?

On 11/12/13 22:14, Sharon Kimble wrote: > On Wed, 11 Dec 2013 21:58:19 +1100 > Scott Ferguson wrote: > >> On 11/12/13 21:45, Sharon Kimble wrote: >>> I have this line in a bash script that is not doing what its >>> supposed to - >>> 'find /home/boudiccas/.fluxbox -type f -mtime +"$num" -name 'me

Re: script line not working as its supposed to, but why?

Mathias Bauer writes: >head -n -7 That's the option I did not recall :) Nice job. -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I c

Re: script line not working as its supposed to, but why?

On Wed, 11 Dec 2013 15:19:22 +0100 Mathias Bauer wrote: > LC_ALL=C ls menu-* | head -n -7 | xargs -r rm Thank you Mathias, I incorporated the line above into the script and it works beautifully, thanks. :) I'll also have a look at the bash tutorials that you posted because I know that they will

Re: script line not working as its supposed to, but why?

Sharon Kimble writes: > ++ wc -l > ++ ls -1 'menu-*' > ls: cannot access menu-*: No such file or directory > + '[' 0 -gt 7 ']' > I fear that you should either 'cd' to the directory (~/.fluxbox I suppose) you want to clear before running my code or change it this way if [ `ls -1 ~/fluxbox/m

Re: script line not working as its supposed to, but why?

* Gian Uberto Lauri wrote on 2013-12-11 at 12:42 (+0100): > Sharon Kimble writes: > > > I want to delete the 'menu-*' files if there are more than 7, > > and the command is parsed when I have 'set -x' at the head of > > the script but this line does nothing! It runs but doesn't > > achieve anythin

Re: script line not working as its supposed to, but why?

On Wed, 11 Dec 2013 12:42:51 +0100 "Gian Uberto Lauri" wrote: > Sharon Kimble writes: > > But there is no consistency with the creation date, the menu > > itself is regenerated whenever I install a new programme, and the > > old menu is saved with the suffix of the date and time. > > > I wan

Re: script line not working as its supposed to, but why?

Sharon Kimble writes: > But there is no consistency with the creation date, the menu itself is > regenerated whenever I install a new programme, and the old menu is > saved with the suffix of the date and time. > I want to delete the 'menu-*' files if there are more than 7, and > the command

Re: script line not working as its supposed to, but why?

On Wed, 11 Dec 2013 12:09:18 +0100 "Gian Uberto Lauri" wrote: > Sharon Kimble writes: > > I have this line in a bash script that is not doing what its > > supposed to - > > 'find /home/boudiccas/.fluxbox -type f -mtime +"$num" -name > > 'menu-*' -delete' > > where "$num" = 7 and 'menu-*'=m

Re: script line not working as its supposed to, but why?

On Wed, 11 Dec 2013 21:58:19 +1100 Scott Ferguson wrote: > On 11/12/13 21:45, Sharon Kimble wrote: > > I have this line in a bash script that is not doing what its > > supposed to - > > 'find /home/boudiccas/.fluxbox -type f -mtime +"$num" -name 'menu-*' > > -delete' > > where "$num" = 7 and 'me

Re: script line not working as its supposed to, but why?

Sharon Kimble writes: > I have this line in a bash script that is not doing what its supposed > to - > 'find /home/boudiccas/.fluxbox -type f -mtime +"$num" -name 'menu-*' > -delete' > where "$num" = 7 and 'menu-*'=menu-20131209-11:05 . Obviously the date > and time can be different in each

Re: script line not working as its supposed to, but why?

On 11/12/13 21:45, Sharon Kimble wrote: > I have this line in a bash script that is not doing what its supposed > to - > 'find /home/boudiccas/.fluxbox -type f -mtime +"$num" -name 'menu-*' > -delete' > where "$num" = 7 and 'menu-*'=menu-20131209-11:05 . Obviously the date > and time can be differ

Re: Script to tell if Qpopper is running.

Account for Debian group mail wrote: > Once in a while the Qpopper on our mail server will just die. I have > to go in and issue a "/etc/init.d/openbsd-inetd restart" and it will > be backup and running. If 'openbsd-inetd restart' fixes it then the problem is that inetd has died not qpopper, right

Re: Script to tell if Qpopper is running.

On Nov 23, 2013, at 1:43 AM, Account for Debian group mail wrote: > "monit" looks like it might work! Monit runs here. It does restart stuff, among a lot of other cool things... -- Glenn English Disclaimer: Any disclaimer attached to this message may be ignored. smime.p7s Description:

Re: Script to tell if Qpopper is running.

Pol, Thanks for the hint... "mon" just alerts you, I have a program that does that already BUT "monit" looks like it might work! Again, thanks! Ken On Sat, 23 Nov 2013, Pol Hallen wrote: Has anyone written a script that will run under a cron job that checks to make sure that the pop3 s

Re: Script to tell if Qpopper is running.

Has anyone written a script that will run under a cron job that checks to make sure that the pop3 server is running and if not will restart it? apt-get install mon Pol -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas..

  1   2   3   4   5   >