Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #270113 > unrolled thread
| Started by | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| First post | 2024-06-16 10:20 +0200 |
| Last post | 2024-06-17 11:00 +0200 |
| Articles | 20 on this page of 125 — 25 participants |
Back to article view | Back to linux.debian.user
Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-16 10:20 +0200
Re: Maximum size .bash_aliases file Richard <rrosner5@gmail.com> - 2024-06-16 15:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-17 10:50 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-16 16:00 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-17 10:30 +0200
Re: Maximum size .bash_aliases file gene heskett <gheskett@shentel.net> - 2024-06-17 13:00 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 13:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-18 10:30 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-18 13:10 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:00 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-17 16:20 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 16:30 +0200
Time, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-17 17:40 +0200
Re: Time, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 17:50 +0200
Re: Time, was Re: Maximum size .bash_aliases file eben@gmx.us - 2024-06-17 19:30 +0200
Re: Time, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:10 +0200
Re: Time, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:10 +0200
Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-17 18:30 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 19:30 +0200
Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-17 19:50 +0200
System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-18 07:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-18 10:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Jeffrey Walton <noloader@gmail.com> - 2024-06-18 10:20 +0200
RTC, was Re: System time/timezone David Wright <deblis@lionunicorn.co.uk> - 2024-06-19 06:10 +0200
Re: RTC, was Re: System time/timezone Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-06-19 21:20 +0200
Re: RTC, was Re: System time/timezone Greg Wooledge <greg@wooledge.org> - 2024-06-19 21:40 +0200
Re: RTC, was Re: System time/timezone Stefan Monnier <monnier@iro.umontreal.ca> - 2024-06-20 04:00 +0200
Re: RTC, was Re: System time/timezone Max Nikulin <manikulin@gmail.com> - 2024-06-20 04:00 +0200
Re: RTC, was Re: System time/timezone Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:20 +0200
Re: RTC, was Re: System time/timezone Michael Stone <mstone@debian.org> - 2024-06-20 05:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-19 06:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-19 06:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-18 13:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-19 06:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-19 13:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Jeffrey Walton <noloader@gmail.com> - 2024-06-19 19:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-20 07:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Jeffrey Walton <noloader@gmail.com> - 2024-06-20 07:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file tomas@tuxteam.de - 2024-06-20 08:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Max Nikulin <manikulin@gmail.com> - 2024-06-21 04:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-21 05:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-21 06:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-22 17:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Stefan Monnier <monnier@iro.umontreal.ca> - 2024-06-22 18:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-06-23 04:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-23 05:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-23 06:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-23 07:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file gene heskett <gheskett@shentel.net> - 2024-06-23 08:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file eben@gmx.us - 2024-06-23 15:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file gene heskett <gheskett@shentel.net> - 2024-06-23 16:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 02:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file eben@gmx.us - 2024-06-26 15:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Curt <curty@free.fr> - 2024-06-24 15:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Curt <curty@free.fr> - 2024-06-24 15:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Bret Busby <bret@busby.net> - 2024-06-24 17:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Heriberto Avelino <heriberto.avelino@gmail.com> - 2024-06-26 00:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Bret Busby <bret@busby.net> - 2024-06-24 17:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file eben@gmx.us - 2024-06-24 18:10 +0200
Re: System time/timezone Felix Miata <mrmazda@earthlink.net> - 2024-06-24 18:20 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file The Wanderer <wanderer@fastmail.fm> - 2024-06-25 00:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file John Hasler <john@sugarbit.com> - 2024-06-25 00:20 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file The Wanderer <wanderer@fastmail.fm> - 2024-06-25 00:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file "Andrew M.A. Cater" <amacater@einval.com> - 2024-06-25 10:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file debian-user@howorth.org.uk - 2024-06-26 12:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file John Hasler <john@sugarbit.com> - 2024-06-26 18:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-26 19:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-28 06:20 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Erwan DAVID <erwan@rail.eu.org> - 2024-06-28 07:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file John Crawley <john@bunsenlabs.org> - 2024-06-28 08:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-28 11:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file John Crawley <john@bunsenlabs.org> - 2024-06-30 03:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-06-25 20:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-25 21:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 03:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 02:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 02:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-23 14:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-24 02:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Curt <curty@free.fr> - 2024-06-23 17:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 02:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-21 13:20 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-22 17:00 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-22 18:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-23 06:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Jeffrey Walton <noloader@gmail.com> - 2024-06-23 07:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-21 06:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Max Nikulin <manikulin@gmail.com> - 2024-06-22 05:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-22 07:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-22 17:20 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-23 04:40 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-23 05:10 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file John Hasler <john@sugarbit.com> - 2024-06-23 21:50 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-26 02:30 +0200
Re: System time/timezone, was Re: Maximum size .bash_aliases file Stefan Monnier <monnier@iro.umontreal.ca> - 2024-06-20 04:00 +0200
time display was: Re: Maximum size .bash_aliases file debian-user@howorth.org.uk - 2024-06-17 17:00 +0200
Re: time display was: Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 17:10 +0200
Re: time display was: Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:20 +0200
Re: time display was: Re: Maximum size .bash_aliases file Default User <hunguponcontent@gmail.com> - 2024-06-22 16:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-20 13:10 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-20 13:20 +0200
Re: Maximum size .bash_aliases file The Wanderer <wanderer@fastmail.fm> - 2024-06-20 13:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:30 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-22 16:10 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-21 06:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-22 10:40 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-22 16:10 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-22 17:00 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-22 18:30 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-23 06:30 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-25 10:40 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-25 13:20 +0200
Re: Maximum size .bash_aliases file debian-user@howorth.org.uk - 2024-06-25 14:30 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-25 15:00 +0200
Australia/Eucla timezone abbreviation (was: Re: Maximum size .bash_aliases file) Max Nikulin <manikulin@gmail.com> - 2024-06-25 17:20 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-22 17:10 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-25 10:50 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-17 06:40 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-17 10:50 +0200
Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-17 11:20 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-17 14:10 +0200
Re: Maximum size .bash_aliases file <tomas@tuxteam.de> - 2024-06-17 14:20 +0200
Re: Maximum size .bash_aliases file Greg Wooledge <greg@wooledge.org> - 2024-06-17 13:30 +0200
Re: Maximum size .bash_aliases file David Wright <deblis@lionunicorn.co.uk> - 2024-06-17 17:50 +0200
Re: Maximum size .bash_aliases file Keith Bainbridge <keithrbau@gmail.com> - 2024-06-17 11:00 +0200
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-16 10:20 +0200 |
| Subject | Maximum size .bash_aliases file |
| Message-ID | <IPThf-3iGI-5@gated-at.bofh.it> |
Good evening Folk
Some of my aliases stopped working after months of working as I
expected. And udating the .bash_aliases kept giving me an error
referring to an end of file before the matching ' in one of the last
aliases. So I did some searching.
(An aside is that a function started failing but see later.)
I found this summary using search.brave.com:
linux maximum bash aliases
Bash aliases are a powerful way to customize your command-line
experience. While there is no strict limit on the number of aliases you
can define, there are some practical limitations to consider.
Practical Limitations
Environment Variables: Bash has a limit on the number of
environment variables it can store, which is typically around 32,000. If
you define too many aliases, you may exceed this limit, causing issues
with your shell.
Shell Scripting: Bash scripts have a limit on the number of
commands they can execute, which is typically around 64,000. If you
define too many aliases, you may exceed this limit, causing issues with
your shell scripts.
/// summary ends
So, is an alias a form of variable? I had about 150 plus 4 functions
So I re-did my .bash_aliases file with only the bits I NEED; and all is
back to normal.
Further searching suggested I could have a .bash_functions file, opened
by .bashrc like .bash_aliases. Guess I could call them anything? but
that only means I have to remember something I do differently from norm.
When I got my aliases working, I checked the size of the old file - 17K.
The new .bash_aliases is 2.5K with .bash_functions at 490B.
The errant function that failed after a little satisfactory use was to
mount a USB and back it up to my system. It is used to run portable apps
at a volunteer job - yes windows. I noticed that the sample functions on
the web didn't have && for each line, so I removed them and performance
is now back to what I expected. The errant line was the mount cmd.
Originally if I had already mounted the USB, the function kept going.
I don't recall adding the &&, so it didn't dawn on me to try removing
them. (I worked around it by unmounting it (an alias) and trying the
back-up again.)
So a question and mybe something related that may help somebody else.
--
All the best
Keith Bainbridge
keithrbau@gmail.com
keith.bainbridge.3216@gmail.com
+61 (0)447 667 468
UTC + 10:00
[toc] | [next] | [standalone]
| From | Richard <rrosner5@gmail.com> |
|---|---|
| Date | 2024-06-16 15:30 +0200 |
| Message-ID | <IPY7f-3lGX-1@gated-at.bofh.it> |
| In reply to | #270113 |
[Multipart message — attachments visible in raw view] — view raw
"And udating the .bash_aliases kept giving me an error referring to an end of file before the matching ' in one of the last aliases." This doesn't refer to a size limitation, but a syntax error. As in: the end of the file was reached before the matching ' was found. Either you mixed " and ' or you simply forgot to close an opened '. Ideally the error message will tell you the affected line. Richard
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-17 10:50 +0200 |
| Message-ID | <IQgdP-3xFP-5@gated-at.bofh.it> |
| In reply to | #270117 |
On 16/6/24 23:20, Richard wrote: > "And udating the .bash_aliases kept giving me an error > referring to an end of file before the matching ' in one of the last > aliases." > > This doesn't refer to a size limitation, but a syntax error. As in: > the end of the file was reached before the matching ' was found. Either > you mixed " and ' or you simply forgot to close an opened '. Ideally the > error message will tell you the affected line. > > Richard Thanks Richard I believe David raised very similar suggestions -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-16 16:00 +0200 |
| Message-ID | <IPYAh-3m1c-1@gated-at.bofh.it> |
| In reply to | #270113 |
On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote: > Environment Variables: Bash has a limit on the number of environment > variables it can store, which is typically around 32,000. If you define too > many aliases, you may exceed this limit, causing issues with your shell. This is not strictly true. There is no limit imposed by bash; but there is a limit imposed by the *kernel* on the total size of the environment plus the argv[] argument vector passed to a process. <https://www.in-ulm.de/~mascheck/various/argmax/> documents this extremely thoroughly. In most cases, when a problem arises with hitting this limit, it's because the argument list is too long, not the environment. You seem to be hitting it from the other direction, though. Solution: "don't do that". > Shell Scripting: Bash scripts have a limit on the number of commands > they can execute, which is typically around 64,000. Well... that sounds like you're filling up the table of exit statuses that have been reaped internally. I think there might have been some bugs in older versions of bash concerning this issue as well. Some people have reported this issue when they run an infinite loop with an external command inside it (e.g. sleep). I don't recall off the top of my head how to work around this issue, if you're writing "daemon scripts" that run forever and spawn external commands within a loop. You might need to Google it. It's a bit esoteric. > If you define too many > aliases, you may exceed this limit, causing issues with your shell scripts. Huh? I have no idea what this means. Bash doesn't have a limit on the number of aliases you can define, as far as I know. Aliases do not work in shell scripts, by default. You would have to turn them on with a shopt. I recommend not doing that. They're disabled because they suck. Use functions instead of aliases, when writing scripts. They're far more sensible and flexible.
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-17 10:30 +0200 |
| Message-ID | <IQfUu-3xza-7@gated-at.bofh.it> |
| In reply to | #270119 |
On 16/6/24 23:50, Greg Wooledge wrote: > On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote: It was late afternoon on 16Jun2024 that I wrote this. Possibly 18:13:36 when I pressed send. I'd reckon it would likely have been 08:13:36 UTC What's wrong with my system clock. I've not really looked at the time on my originals before. I'll try to remember to enter my local time as I press send >> Environment Variables: Bash has a limit on the number of environment >> variables it can store, which is typically around 32,000. If you define too >> many aliases, you may exceed this limit, causing issues with your shell. > > This is not strictly true. There is no limit imposed by bash; but > there is a limit imposed by the *kernel* on the total size of the > environment plus the argv[] argument vector passed to a process. > > <https://www.in-ulm.de/~mascheck/various/argmax/> documents this > extremely thoroughly. > > In most cases, when a problem arises with hitting this limit, it's > because the argument list is too long, not the environment. You seem > to be hitting it from the other direction, though. > > Solution: "don't do that". > >> Shell Scripting: Bash scripts have a limit on the number of commands >> they can execute, which is typically around 64,000. Thanks Greg Your comments on the summary provided by the search engine will make me read them with a bigger grain of salt. > > Well... that sounds like you're filling up the table of exit statuses > that have been reaped internally. I think there might have been some > bugs in older versions of bash concerning this issue as well. Ummm could I be doing this without knowing what it means? > > Some people have reported this issue when they run an infinite loop with > an external command inside it (e.g. sleep). I have 1 sleep line in what is now a function. It was added in an effort to get the USB to unmount after the back-up process and cd to~. I did get a command prompt back, but the USB was still mounted according to df > > I don't recall off the top of my head how to work around this issue, if > you're writing "daemon scripts" that run forever and spawn external > commands within a loop. You might need to Google it. It's a bit > esoteric. And I'd suggest beyond me > >> If you define too many >> aliases, you may exceed this limit, causing issues with your shell scripts. > > Huh? I have no idea what this means. Bash doesn't have a limit on the > number of aliases you can define, as far as I know. This is again part of the search engine synopsis > > Aliases do not work in shell scripts, by default. You would have to turn > them on with a shopt. I recommend not doing that. They're disabled > because they suck. Use functions instead of aliases, when writing scripts. > They're far more sensible and flexible. You are re-enforcing other stuff I read last night. > I hope this and my several other responses find you bright and bubbly on a Monday morning. I'm home from a day of cryptic crossword class, and minding 2 month old grand daughter etc. I hope my responses aren't too short. the time is 17Jun2024@18:25:58 -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-06-17 13:00 +0200 |
| Message-ID | <IQifJ-3yXM-9@gated-at.bofh.it> |
| In reply to | #270143 |
On 6/17/24 04:26, Keith Bainbridge wrote: > > On 16/6/24 23:50, Greg Wooledge wrote: >> On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote: > > It was late afternoon on 16Jun2024 that I wrote this. Possibly 18:13:36 > when I pressed send. I'd reckon it would likely have been 08:13:36 UTC > What's wrong with my system clock. I've not really looked at the time > on my originals before. I'll try to remember to enter my local time as > I press send You are not running an ntp client? I do, and in turn I am a stratum 2 server for most of my other machines here. So my system is withing a millisecond of the atomic clocks in Colorado Springs. It's no big deal. use ntpsec if up 24/7, or chrony if you shut down. ntpsec works if already in time but can't slam to the correct time if not synchronized, chrony can sync after long downtimes. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-17 13:30 +0200 |
| Message-ID | <IQiIF-3zm4-11@gated-at.bofh.it> |
| In reply to | #270143 |
On Mon, Jun 17, 2024 at 06:26:19PM +1000, Keith Bainbridge wrote: > On 16/6/24 23:50, Greg Wooledge wrote: > > On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote: > > It was late afternoon on 16Jun2024 that I wrote this. Possibly 18:13:36 when > I pressed send. I'd reckon it would likely have been 08:13:36 UTC What's > wrong with my system clock. I've not really looked at the time on my > originals before. I'll try to remember to enter my local time as I press > send What does "date" say? Paste the entire output. What does "cat /etc/timezone" say? Paste the entire output. What does "ls -l /etc/localtime" say? Paste the entire output. Have you set the TZ environment variable? If so, what did you set it to? What time zone are you *actually* in? Like, what country, and what major city is nearest to you? Which NTP client are you running? Have you checked up on it, to make sure it's actually running, properly configured, and not spewing errors?
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-18 10:30 +0200 |
| Message-ID | <IQCo1-3LJB-15@gated-at.bofh.it> |
| In reply to | #270153 |
On 17/6/24 21:22, Greg Wooledge wrote: > On Mon, Jun 17, 2024 at 06:26:19PM +1000, Keith Bainbridge wrote: >> On 16/6/24 23:50, Greg Wooledge wrote: >>> On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote: >> It was late afternoon on 16Jun2024 that I wrote this. Possibly 18:13:36 when >> I pressed send. I'd reckon it would likely have been 08:13:36 UTC What's >> wrong with my system clock. I've not really looked at the time on my >> originals before. I'll try to remember to enter my local time as I press >> send I'm back. The kitchen clock says 18:05. the sun has set. I have no reason to doubt the clock. So I'll answer Greg's questions > What does "date" say? Paste the entire output. $> date Tue 18 Jun 2024 18:06:31 AEST > > What does "cat /etc/timezone" say? Paste the entire output. cat /etc/timezone Australia/Melbourne is as close as I can specify for my regional city > > What does "ls -l /etc/localtime" say? Paste the entire output. ls -l /etc/localtime lrwxrwxrwx 1 root root 39 Mar 4 21:00 /etc/localtime -> /usr/share/zoneinfo/Australia/Melbourne > Have you set the TZ environment variable? If so, what did you set it to? Not that I'm aware of > What time zone are you *actually* in? Like, what country, and what major > city is nearest to you? UTC +10:00 Australia, Geelong Our capital is Melbourne > > Which NTP client are you running? Have you checked up on it, to make > sure it's actually running, properly configured, and not spewing errors? No, but why, when I believe everything I have answered is correct. If it helps, I have the date as part of my command prompt, always appears right time after an enter; aliases and desktop short-cuts that give me the date and time reliably so far. Greg, if there is something not right with my answer, please let me know. Again thanks greatly for your help. I saw another response about how the MUA deals with the senders date when replying. So fired up claws and sent myself a brief note. when replying to myself, the reply quoted On 18/6/24 17:56, Keith Bainbridge wrote: When forwarding that same note, the forward quoted -------- Forwarded Message -------- Subject: test sent date details Date: Tue, 18 Jun 2024 17:56:41 +1000 From: Keith Bainbridge <keithrbau@gmail.com> To: keithrbau@gmail.com I'll forward this asap, to confirm the detail. Guess I could also alter address in a reply to send it here as well. Look for it shortly as well. This makes me think that I need to adjust my MUA settings; thunderbird for this mail and my normal mail use; and claws for some use. claws has reply and forwarding templates with place holders for date formats amongst other items. I'll play around there as it's easier to start with. Item 1 will be change the date to read as it does in the forward Tue 18Jun2024. Thanks all for your responses. I'll go through them all later tonight > -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-18 13:10 +0200 |
| Message-ID | <IQESR-3NjL-3@gated-at.bofh.it> |
| In reply to | #270202 |
On Tue, Jun 18, 2024 at 18:26:39 +1000, Keith Bainbridge wrote: > I'm back. The kitchen clock says 18:05. the sun has set. I have no reason to > doubt the clock. So I'll answer Greg's questions > > > What does "date" say? Paste the entire output. > $> date > Tue 18 Jun 2024 18:06:31 AEST > > > > > What does "cat /etc/timezone" say? Paste the entire output. > > cat /etc/timezone > Australia/Melbourne > > is as close as I can specify for my regional city > > > > What does "ls -l /etc/localtime" say? Paste the entire output. > ls -l /etc/localtime > lrwxrwxrwx 1 root root 39 Mar 4 21:00 /etc/localtime -> > /usr/share/zoneinfo/Australia/Melbourne > > > Have you set the TZ environment variable? If so, what did you set it to? > Not that I'm aware of > > What time zone are you *actually* in? Like, what country, and what major > > city is nearest to you? > > UTC +10:00 > > Australia, Geelong Our capital is Melbourne So, everything looks fine here. > Greg, if there is something not right with my answer, please let me know. > Again thanks greatly for your help. In a previous message, you thought that your system clock or your time zone was set wrong, because you read one of the attribution lines of one of my replies, and you thought it said you had sent your message at the wrong time. As it turns out, I'm fairly certain you misread the attribution line, which was reporting time in a 12-hour format, with "PM". You saw the 06:... and thought it was saying you had sent your email at 6 AM, but you missed the "PM" at the end. As far as I know, it was a simple misread on your part, and nothing is actually wrong. In fact, things should be even better now, because you provoked me into reading about mutt's attribution and date_format variables, and changing the silly default format to a more sensible format. You'll note that this reply uses an attribution with a 24-hour format.
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-22 10:00 +0200 |
| Message-ID | <IS3Pb-4GTO-9@gated-at.bofh.it> |
| In reply to | #270210 |
On 18/6/24 21:02, Greg Wooledge wrote: > In a previous message, you thought that your system clock or your time > zone was set wrong, because you read one of the attribution lines of > one of my replies, and you thought it said you had sent your message > at the wrong time. > > As it turns out, I'm fairly certain you misread the attribution line, > which was reporting time in a 12-hour format, with "PM". You saw the > 06:... and thought it was saying you had sent your email at 6 AM, but > you missed the "PM" at the end. > > As far as I know, it was a simple misread on your part, and nothing is > actually wrong. Absolutely correct Greg. I like your date/time line. The addition of the offset fro UTC without some explanation confused me. And started 2 debates. -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2024-06-17 16:20 +0200 |
| Message-ID | <IQlnb-3B63-3@gated-at.bofh.it> |
| In reply to | #270143 |
On Mon 17 Jun 2024 at 18:26:19 (+1000), Keith Bainbridge wrote:
> On 16/6/24 23:50, Greg Wooledge wrote:
> > On Sun, Jun 16, 2024 at 06:13:36PM +1000, Keith Bainbridge wrote:
>
> It was late afternoon on 16Jun2024 that I wrote this. Possibly
> 18:13:36 when I pressed send. I'd reckon it would likely have been
> 08:13:36 UTC What's wrong with my system clock. I've not really
> looked at the time on my originals before. I'll try to remember to
> enter my local time as I press send
All the mail clients I've used apply the timestamp when you press
Send. You live in eastern Australia, I assume, and if you observe
DST at all, it won't be now.
Your attribution could benefit from having some indication of the
timezone that /it/ uses: Greg was writing in the morning, not near
midnight. But your clock is OK, as shown by the headers in your
postings:
sending: Date: Sun, 16 Jun 2024 18:13:36 +1000
processing: Received: from mail-oi1-x233.google.com …
by bendel.debian.org …
Sun, 16 Jun 2024 08:13:48 +0000 (UTC)
You asked after your /system/ clock. I don't think I can tell whether
it's set to UTC or Local Time, but only that it is correct, whichever
it it on. Likewise the hardware RTC. The third line of /etc/adjtime
says what the RTC is on; /etc/timezone says what the system is on;
$ date says what your user is on.
> I hope this and my several other responses find you bright and bubbly
> on a Monday morning. I'm home from a day of cryptic crossword class,
> and minding 2 month old grand daughter etc. I hope my responses aren't
> too short.
>
> the time is 17Jun2024@18:25:58
>
> keithrbau@gmail.com
> keith.bainbridge.3216@gmail.com
> +61 (0)447 667 468
>
> UTC + 10:00
Looks fine to me. Mobile numbers are a separate sequence like in the
UK, aren't they, and unlike in the US.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-17 16:30 +0200 |
| Message-ID | <IQlwR-3B9w-5@gated-at.bofh.it> |
| In reply to | #270165 |
On Mon, Jun 17, 2024 at 09:14:38AM -0500, David Wright wrote: > You asked after your /system/ clock. I don't think I can tell whether > it's set to UTC or Local Time, but only that it is correct, whichever > it it on. Likewise the hardware RTC. The third line of /etc/adjtime > says what the RTC is on; /etc/timezone says what the system is on; > $ date says what your user is on. /etc/timezone is only used by some legacy programs. All the current ones should be using /etc/localtime instead, which is a symlink to a binary zoneinfo file, rather than a text file containing a timezone name. I wonder if Keith's confusion is simply due to my MUA using "AM" and "PM" in its attribution line, and Keith not seeing the "PM". Maybe I should look into configuring that differently.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2024-06-17 17:40 +0200 |
| Subject | Time, was Re: Maximum size .bash_aliases file |
| Message-ID | <IQmCB-3BMU-19@gated-at.bofh.it> |
| In reply to | #270166 |
On Mon 17 Jun 2024 at 10:23:46 (-0400), Greg Wooledge wrote: > On Mon, Jun 17, 2024 at 09:14:38AM -0500, David Wright wrote: > > You asked after your /system/ clock. I don't think I can tell whether > > it's set to UTC or Local Time, but only that it is correct, whichever > > it it on. Likewise the hardware RTC. The third line of /etc/adjtime > > says what the RTC is on; /etc/timezone says what the system is on; > > $ date says what your user is on. > > /etc/timezone is only used by some legacy programs. All the current > ones should be using /etc/localtime instead, which is a symlink to a > binary zoneinfo file, rather than a text file containing a timezone name. You're right of course, but confirming its value does involve using a command that's probably not at the front of one's mind. BTW what's the relationship between "current programs" and TZ nowadays? > I wonder if Keith's confusion is simply due to my MUA using "AM" and "PM" > in its attribution line, and Keith not seeing the "PM". Maybe I should > look into configuring that differently. Along with 350M Americans! They even use just A and P over here. And a mere dot on digital clocks. (I see you've changed it already!) Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-17 17:50 +0200 |
| Subject | Re: Time, was Re: Maximum size .bash_aliases file |
| Message-ID | <IQmMh-3BQu-11@gated-at.bofh.it> |
| In reply to | #270172 |
On Mon, Jun 17, 2024 at 10:36:59 -0500, David Wright wrote: > On Mon 17 Jun 2024 at 10:23:46 (-0400), Greg Wooledge wrote: > > /etc/timezone is only used by some legacy programs. All the current > > ones should be using /etc/localtime instead, which is a symlink to a > > binary zoneinfo file, rather than a text file containing a timezone name. > > You're right of course, but confirming its value does involve using > a command that's probably not at the front of one's mind. > > BTW what's the relationship between "current programs" and TZ nowadays? Do you mean the TZ variable? That overrides the system default. hobbit:~$ date; TZ=Europe/Paris date Mon Jun 17 11:40:59 EDT 2024 Mon Jun 17 17:40:59 CEST 2024 If you're asking about programs that still use /etc/timzeone, I don't know of any off hand. I'd be interested in hearing about any that still do, though probably less so than the Debian libc6 maintainers are.
[toc] | [prev] | [next] | [standalone]
| From | eben@gmx.us |
|---|---|
| Date | 2024-06-17 19:30 +0200 |
| Subject | Re: Time, was Re: Maximum size .bash_aliases file |
| Message-ID | <IQol4-3CVf-19@gated-at.bofh.it> |
| In reply to | #270172 |
On 6/17/24 11:36, David Wright wrote: > On Mon 17 Jun 2024 at 10:23:46 (-0400), Greg Wooledge wrote: >> I wonder if Keith's confusion is simply due to my MUA using "AM" and "PM" >> in its attribution line, and Keith not seeing the "PM". Maybe I should >> look into configuring that differently. > > Along with 350M Americans! They even use just A and P over here. And a > mere dot on digital clocks. And I can never remember if the dot means AM or PM. I suspect it changes between implementations, or maybe I'm just very slow. Worse(?), some clocks that don't deal with date or alarms (e.g. microwave, car, some watches) are 12h only. -- Given the correlation between insufficient nookie and the high rate of unemployment among recent college graduates coupled with high college debts, I propose to kill two birds* with one stone: A new government program called "Ameriwhore". -- Arty in AFC-A
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-22 10:10 +0200 |
| Subject | Re: Time, was Re: Maximum size .bash_aliases file |
| Message-ID | <IS3YR-4Hcl-3@gated-at.bofh.it> |
| In reply to | #270177 |
On 18/6/24 03:24, eben@gmx.us wrote: > > And I can never remember if the dot means AM or PM. I suspect it changes > between implementations, or maybe I'm just very slow. Probably only really meant to show us when we are setting an alarm at night, for the morning, that the dot is on one and off on the other. Else we'll wake a little late. Remember the joke about going to bed at 8 and setting the alarm on a wind-up clock for 9 - we wouldn't get much sleep. -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | Keith Bainbridge <keithrbau@gmail.com> |
|---|---|
| Date | 2024-06-22 10:10 +0200 |
| Subject | Re: Time, was Re: Maximum size .bash_aliases file |
| Message-ID | <IS3YR-4Hcl-5@gated-at.bofh.it> |
| In reply to | #270172 |
On 18/6/24 01:36, David Wright wrote: > Along with 350M Americans! They even use just A and P over here. And a > mere dot on digital clocks. (I see you've changed it already!) I've been using 24 hour time and dMMMyyyy for a long time. I used send international cheques as part of my work, and decided that spelling the month was simple basics. -- All the best Keith Bainbridge keithrbau@gmail.com keith.bainbridge.3216@gmail.com +61 (0)447 667 468 UTC + 10:00
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-06-17 18:30 +0200 |
| Message-ID | <IQnoZ-3Cjq-13@gated-at.bofh.it> |
| In reply to | #270165 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Jun 17, 2024 at 09:14:38AM -0500, David Wright wrote: [...] > You asked after your /system/ clock. I don't think I can tell whether > it's set to UTC or Local Time, but only that it is correct, whichever > it it on. Likewise the hardware RTC. The third line of /etc/adjtime > says what the RTC is on; /etc/timezone says what the system is on; > $ date says what your user is on. No: /etc/timezone just says what time zone a _user_ will "get" unless they state otherwise. I.e. a user's default time zone. The "system" being "on" a timezone is something that, under Unix, doesn't make sense. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-06-17 19:30 +0200 |
| Message-ID | <IQol4-3CVf-43@gated-at.bofh.it> |
| In reply to | #270176 |
On Mon, Jun 17, 2024 at 18:22:29 +0200, tomas@tuxteam.de wrote: > On Mon, Jun 17, 2024 at 09:14:38AM -0500, David Wright wrote: > > [...] > > > You asked after your /system/ clock. I don't think I can tell whether > > it's set to UTC or Local Time, but only that it is correct, whichever > > it it on. Likewise the hardware RTC. The third line of /etc/adjtime > > says what the RTC is on; /etc/timezone says what the system is on; > > $ date says what your user is on. > > No: /etc/timezone just says what time zone a _user_ will "get" unless > they state otherwise. I.e. a user's default time zone. > > The "system" being "on" a timezone is something that, under Unix, > doesn't make sense. Time zones are not in effect for users, either; they're in effect for processes. A given user's login session, which is a collection of processes, would typically all be using the same time zone, for consistency, but this isn't necessary. They might choose to run two clocks, one in their local time zone, and one in another time zone, where a family member lives, or where they're about to take a vacation. /etc/localtime points to the time zone that a process will use if it doesn't specify one via the TZ environment variable. And /etc/timezone is the legacy version of /etc/localtime.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-06-17 19:50 +0200 |
| Message-ID | <IQoEp-3D1W-7@gated-at.bofh.it> |
| In reply to | #270178 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Jun 17, 2024 at 01:20:53PM -0400, Greg Wooledge wrote: [...] > > The "system" being "on" a timezone is something that, under Unix, > > doesn't make sense. > > Time zones are not in effect for users, either; they're in effect for > processes [...] Right you are. Cheers -- t
[toc] | [prev] | [next] | [standalone]
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
Back to top | Article view | linux.debian.user
csiph-web