Le 14/12/2019 à 16:35, Ottavio Caruso a écrit :
On Sat, 14 Dec 2019 at 13:47, Pascal Hambourg wrote:
Le 14/12/2019 à 14:20, Ottavio Caruso a écrit :
I've also added:
GRUB_CMDLINE_LINUX_DEFAULT="resume d823f1ee-2e16-4327-b0c1-639f377002bb"
Wrong syntax. It should be "resume=UUID=d823...".
On Sat, 14 Dec 2019 at 13:47, Pascal Hambourg wrote:
>
> Le 14/12/2019 à 14:20, Ottavio Caruso a écrit :
> (...)
> > I've also added:
> > GRUB_CMDLINE_LINUX_DEFAULT="resume d823f1ee-2e16-4327-b0c1-639f377002bb"
>
> Wrong syntax. It should be "resume=UUID=d823...".
> This will override the RESUME
Le 14/12/2019 à 14:20, Ottavio Caruso a écrit :
$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-4.9.0-11-amd64
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=d823f1ee-2e16-4327-b0c1-639f377002bb)
I: Set the RESUME variable to override this.
Le 14/12/2019 à 12:26, Ottavio Caruso a écrit :
$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-4.9.0-11-amd64
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=d823f1ee-2e16-4327-b0c1-639f377002bb)
I: Set the RESUME variable to override this.
I'll
Le 14/12/2019 à 10:43, Alexander V. Makartsev a écrit :
Simple swap partition creation is not enough for hibernation to work, it
also has to be configured in initrd. [2]
Despite the file name it is no longer an initrd but an initramfs.
On 13.12.2019 23:44, Ottavio Caruso wrote:
> Hi,
>
> I'm running LMDE3 (based on Debian oldstable) on Thinkpad Edge E130.
> I'm not getting much support lately from the Mint forums and that's
> why I'm posting here.
>
> This laptop had been running happily with a mere 4GB RAM and no swap
> until
Thanks -- I'll try that sometime tomorrow!
On Tuesday, December 03, 2019 07:24:49 PM David wrote:
> On Wed, 4 Dec 2019 at 01:36, wrote:
> > I always have trouble with all the rigamarole around quoting for the
> > shell vs. quoting for the regex (or quoting or not quoting for anything
> > else).
On Wed, 4 Dec 2019 at 01:36, wrote:
> I always have trouble with all the rigamarole around quoting for the shell vs.
> quoting for the regex (or quoting or not quoting for anything else).
>
> I don't know what it will take to get it to sink into my head. (Maybe in my
> next life ;-)
Hi, yes,
On Tue, Dec 03, 2019 at 10:18:59AM -0500, Stefan Monnier wrote:
> > I think the canonical name is "metasyntactic variable" [1]. I've
> > seen also just "metavariable", although Wikipedia would say that
> > the latter belongs in the realm of logic [2], not programming.
>
> AFAICT those two usages
> I think the canonical name is "metasyntactic variable" [1]. I've
> seen also just "metavariable", although Wikipedia would say that
> the latter belongs in the realm of logic [2], not programming.
AFAICT those two usages are one and the same: when you see "foo" it's
because the code is actually
On Ma, 03 dec 19, 15:09:45, Jonas Smedegaard wrote:
>
> What I have so far settled on is to distinguish "variables" in capital
> letters, and explicitly hint that it should be changed, like this:
>
> With 'find' instead of 'locate' (adapt dir):
>
> find DIR_WITH_REPOS -type d -name .git
>
>
On Tue, Dec 03, 2019 at 08:07:16AM -0500, rhkra...@gmail.com wrote:
[...]
> On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote:
> > With 'find' instead of 'locate'.
[...]
> It took me a minute (well, a trial) to realize that dir_with_repos is a
> metaname (right word?). I prefer a
On Tuesday, December 03, 2019 09:01:16 AM Greg Wooledge wrote:
> On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote:
> > locate --regex \/\.gitignore
>
> Your quoting is all wrong here. What you want is:
>
> locate --regex '/\.gitignore'
>
> The / does not need to be quoted, either for
On Tuesday, December 03, 2019 09:09:45 AM Jonas Smedegaard wrote:
> With 'find' instead of 'locate' (adapt dir):
>
> find DIR_WITH_REPOS -type d -name .git
That helps, also, especially with the note "adapt dir" (or maybe "adjust dir",
or "specify dir appropriately" (I don't know why I'm
On Tuesday, December 03, 2019 08:39:28 AM Brian wrote:
> On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote:
> > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote:
> > > With 'find' instead of 'locate'.
> > >
> > > find dir_with_repos -type d -name .git
> > >
> > >
Quoting Brian (2019-12-03 14:39:28)
> On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote:
>
> > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote:
> > > With 'find' instead of 'locate'.
> > >
> > > find dir_with_repos -type d -name .git
> > >
> > > or
> > >
> > >
On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote:
> locate --regex \/\.gitignore
Your quoting is all wrong here. What you want is:
locate --regex '/\.gitignore'
The / does not need to be quoted, either for the shell, or for the
regex. It's just a regular old character with no special
On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote:
> On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote:
> > With 'find' instead of 'locate'.
> >
> > find dir_with_repos -type d -name .git
> >
> > or
> >
> > find dir_with_repos -type d -name "*.git"
> >
> > if
Andrei,
Thanks very much! (Please forgive the nitpicky comment below.)
On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote:
> With 'find' instead of 'locate'.
>
> find dir_with_repos -type d -name .git
>
> or
>
> find dir_with_repos -type d -name "*.git"
>
> if you also
On Ma, 03 dec 19, 05:54:33, Rh Kramer wrote:
> Notes:
>
>* In general, reply to the list, I am subscribed under a slightly
> different
> username and will see any replies.
>
>* As is often the case, there is more than one way to skin this cat,
> although I won't mind other approaches,
@s31:/rhk03$ locate --regex \/\.git[^\/][:blank:]
> rhk@s31:/rhk03$ locate --regex \/git[^\.][:blank:]
> rhk@s31:/rhk03$ locate --regex \.git[^\.][:blank:]
> rhk@s31:/rhk03$ locate --regex \.git[\.][:blank:]
> rhk@s31:/rhk03$ locate --regex \.git[:blank:]
>
> Any help / insights will be appreciated!
:/rhk03$ locate --regex \/\.git[^\/][:blank:]
rhk@s31:/rhk03$ locate --regex \/git[^\.][:blank:]
rhk@s31:/rhk03$ locate --regex \.git[^\.][:blank:]
rhk@s31:/rhk03$ locate --regex \.git[\.][:blank:]
rhk@s31:/rhk03$ locate --regex \.git[:blank:]
Any help / insights will be appreciated!
On Monday 02 December 2019 04:35:26 Andrei POPESCU wrote:
> On Du, 01 dec 19, 22:28:43, Gene Heskett wrote:
> > It, iptables, did not get restarted on the fresh boot, so obviously
> > the systemd manager hasn't been informed to start iptables,
> > reloading from /etc/iptables/saved-rules.
>
> To
ent timer
I have asked to isc DHCP users but no one give me a tips actually :
https://lists.isc.org/pipermail/dhcp-users/2019-October/021886.html
Thanks for your help !
Baptiste
On Mi, 18 sep 19, 14:40:29, Prunk Dump wrote:
>
> -> Maybe a bug in the systemd configuration files that awake service
> in wrong order ? ( I will do soon a not related bug report to Debian,
> puppet.service does not contain any "After=" line )
>
> -> Maybe a bug in network-manager when the host
Baptiste, on 2019-09-18:
> So with you help here my current check list :
> -> Maybe a bug in the resolv.conf file access just after the suspend
> recover. I need to find who is accessing the file and when. And why
> this prevent DNS resolution working.
>
> -> Ma
Thanks you very much Etienne for your help ! I will try to give as
much precision as possible using your tips.
Le mar. 17 sept. 2019 à 23:13, Étienne Mollier
a écrit :
>
> Baptiste, on 2019-09-17:
> > I have two critical systemd services running on my clients :
> > ->
Baptiste, on 2019-09-17:
> I have two critical systemd services running on my clients :
> -> "puppet" that ensure propagation of my whole network configuration.
> -> "samba winbind" that allow users pam authentication and Name Service
> Switch.
> These two services use DNS to find their services
Hello Debian Team !
I'm the network Administrator of a french High School and I have
troubles debugging a DNS lookup problem affecting all my 550 Debian
Buster clients.
I have two critical systemd services running on my clients :
-> "puppet" that ensure propagation of my whole network
On 8/25/19, Daniel Rossi wrote:
> I've tried to figure out this myself, but have been forced here. I need
> to enable a feature which was added in git but not packaged for buster
> yet, I have exactly the same problem with Ubuntu Bionic. I would like to
> make unstable packages of this for
ild.
This project has a build system, but it was also a failure and gave up
with it, not getting much help to resolve debian packages problems and
it includes system files.
Let me know.
I would appreciate it since y’all received it
Sent from my iPhone
's buffer.
>
> Really, my first step is to turn the printer off or press pause (if there is
> a pause button). If I had pressed pause, I then turn the printer off to let
> the buffer clear.
Thanks to all for help. My case was, I think, the one described: even canceled
the jobs from
On Thursday, June 13, 2019 12:12:21 PM Eduardo M KALINOWSKI wrote:
> But often the job does not appear anymore in the queue anymore because
> the computer has finished sending it to the printer. In this case you
> have to cancel in the printer, if it provides an option for that.
When I have that
On qui, 13 jun 2019, Rodolfo Medina wrote:
Thanks. Solved. I deleted the printer from Cups managing section and then
added it again. It still printed another few pages and then
stopped. But next
time...?
There should be a way to view the queue from the Cups web interface
(which I
Hi,
On 13/06/2019 18:31, Dan Ritter wrote:
> Rodolfo Medina wrote:
>> Hi...
>>
>> by mistake I told my Samsung ML-1925 to print a large document and don't
>> manage
>> to cancel that... I tried with the `cancel' command, also lprm, and also
>> from
>> within web browser print management...
Dan Ritter writes:
> Rodolfo Medina wrote:
>> Hi...
>>
>> by mistake I told my Samsung ML-1925 to print a large document and don't
>> manage to cancel that... I tried with the `cancel' command, also lprm, and
>> also from within web browser print management... but nothing, it goes on
>>
Rodolfo Medina wrote:
> Hi...
>
> by mistake I told my Samsung ML-1925 to print a large document and don't
> manage
> to cancel that... I tried with the `cancel' command, also lprm, and also from
> within web browser print management... but nothing, it goes on wanting to
> print it still.
and more, please anyone
tell me how to stop it.
Thanks for any help,
Rodolfo
Hi I'm Alexandria F., I'm working in a DebianCustomCD(
https://wiki.debian.org/DebianCustomCD ), I'm a software developer, i have all
versions of your distributions of debian jessie and
stretch(gnome,kde,xfce,cinnamon,lxde) downloaded, but im start in contact with
you because i have some
On Fri, May 24, 2019 at 03:02:52AM +, Ale Frataslafra wrote:
Hello, I'm Alexandria F., I'm a software developer, i have all versions
of your distributions of debian jessie and
stretch(gnome,kde,xfce,cinnamon,lxde) downloaded, but im start in
contact with you because i have some questions
Hello, I'm Alexandria F., I'm a software developer, i have all versions of your
distributions of debian jessie and stretch(gnome,kde,xfce,cinnamon,lxde)
downloaded, but im start in contact with you because i have some questions
about debian live cd, for be specific(Jessie 8.0.0), my questions
Just to provide an update -- the current status is that the beep is not
occurring atm, but it has been just a little cooler. If I get a chance, I'll
take that machine down and clean out any dust and such, or, if the beeping
resumes I'll try some of the ideas suggested here.
As an aside, the
On Thu 09 May 2019 at 20:46:34 (+0200), Jan Claeys wrote:
> On Thu, 2019-05-09 at 09:56 +, Curt wrote:
> > In the event there is no functional motherboard speaker, I guess it
> > cannot be a BIOS alarm of any kind.
>
> Some on-board audio chips are wired up so that they can emulate old
>
On Thu, 2019-05-09 at 09:56 +, Curt wrote:
> In the event there is no functional motherboard speaker, I guess it
> cannot be a BIOS alarm of any kind.
Some on-board audio chips are wired up so that they can emulate old
school IBM PC compatible motherboard speakers/buzzers.
--
Jan Claeys
On Thursday, May 09, 2019 10:08:41 AM Martin wrote:
> I had this looong time ago. Caused by a noisy/broken keyboard cable. My be
> there could be a situation similar on modern USB base keyboards?
Thanks for the reply!
I'll watch for hints that could be the problem -- I use one keyboard / mouse /
On 2019-05-09, rhkra...@gmail.com wrote:
>
>> In the event there is no functional motherboard speaker, I guess it
>> cannot be a BIOS alarm of any kind.
>
> Interesting -- I'm not used to / familiar with a speaker on the MB -- in the
> old days there was typically a speaker in the case that (if
On Thursday 09 May 2019 09:57:38 am Gene Heskett wrote:
> On Thursday 09 May 2019 05:56:58 am Curt wrote:
> > On 2019-05-09, Cindy Sue Causey wrote:
> > > I had something similar that sounded like a little 6" Elf sneezing
> > > in my little ASUS laptop/netbook. Same deal where it was very
> > >
Am 09.05.19 um 02:32 schrieb rhkra...@gmail.com:
> On my Debian Jessie system, for several hours today I've been hearing a beep
> (through my audio system / speakers / headphones) something like the beep
> that
> used to come out of the PC speaker (on older computers -- I don't think I
> even
On Thursday 09 May 2019 05:56:58 am Curt wrote:
> On 2019-05-09, Cindy Sue Causey wrote:
> > I had something similar that sounded like a little 6" Elf sneezing
> > in my little ASUS laptop/netbook. Same deal where it was very
> > sporadic. It turned out to most likely be a warning that it was
>
Thanks to all who replied -- see below:
On Thursday, May 09, 2019 02:10:16 AM Cindy Sue Causey wrote:
> On 5/8/19, Charlie Kravetz wrote:
> > Possibly an open website? Some of those become very annoying.
I'll look into that -- thankfully that is the computer that probably has only
30 to 40
On 2019-05-09, Cindy Sue Causey wrote:
>
>
> I had something similar that sounded like a little 6" Elf sneezing in
> my little ASUS laptop/netbook. Same deal where it was very sporadic.
> It turned out to most likely be a warning that it was about to *CLICK*
> off due to overheating..
>
> $
On 5/8/19, Charlie Kravetz wrote:
> On Wed, 8 May 2019 20:32:49 -0400
> rhkra...@gmail.com wrote:
>
>>On my Debian Jessie system, for several hours today I've been hearing a
>> beep
>>(through my audio system / speakers / headphones) something like the beep
>> that
>>used to come out of the PC
On Wed, 8 May 2019 20:32:49 -0400
rhkra...@gmail.com wrote:
>On my Debian Jessie system, for several hours today I've been hearing a beep
>(through my audio system / speakers / headphones) something like the beep that
>used to come out of the PC speaker (on older computers -- I don't think I
On my Debian Jessie system, for several hours today I've been hearing a beep
(through my audio system / speakers / headphones) something like the beep that
used to come out of the PC speaker (on older computers -- I don't think I even
have that speaker connected on this computer).
The beep
On Wed, 8 May 2019 14:31:35 -0400
Gene Heskett wrote:
>
> And this is windows 10 HOME EDITION, so there is no place to "run as
> admin" in the start menu's.
>
It can't join a domain, but otherwise there's not much difference in
versions.
>
> Anyway, in Home Edition of W10, how the heck do
On Wed, 8 May 2019 14:09:16 -0400
Gene Heskett wrote:
>
> I'm also well pleased that I'm not being chastised for winders here,
> thank you very much for that.
On the whole, Debian is for grown-ups, not the Linux nutters. I've
earned a fair bit of money from Windows in the past, and I still
On Wednesday 08 May 2019 04:55:47 am john doe wrote:
> On 5/8/2019 10:24 AM, Gene Heskett wrote:
> > On Wednesday 08 May 2019 03:49:34 am Joe wrote:
> >> On Tue, 7 May 2019 18:47:50 -0400
> >>
> >> Gene Heskett wrote:
> >>> Greetings all;
> >>>
> >>> First it doesn't have a clue what to do with
On Wednesday 08 May 2019 04:55:47 am john doe wrote:
> On 5/8/2019 10:24 AM, Gene Heskett wrote:
> > On Wednesday 08 May 2019 03:49:34 am Joe wrote:
> >> On Tue, 7 May 2019 18:47:50 -0400
> >>
> >> Gene Heskett wrote:
> >>> Greetings all;
> >>>
> >>> First it doesn't have a clue what to do with
On 2019-05-08, Gene Heskett wrote:
>
> That is a laborius process, taking at least 10x what any of my linux
> machines need to reboot. From powerup to login was at least 15 minutes.
>
> And I have been to that utility, but it has no place to disable ipv6 as a
> whole, has lots of names in the
On 5/8/2019 10:24 AM, Gene Heskett wrote:
> On Wednesday 08 May 2019 03:49:34 am Joe wrote:
>
>> On Tue, 7 May 2019 18:47:50 -0400
>>
>> Gene Heskett wrote:
>>> Greetings all;
>>>
>>> First it doesn't have a clue what to do with a wired network.
>>> It sure wants to hook up to all the
On Wed, 8 May 2019 03:55:03 -0400
Gene Heskett wrote:
>
> That is a laborius process, taking at least 10x what any of my linux
> machines need to reboot. From powerup to login was at least 15
> minutes.
Very definitely not right. Maybe it feels outnumbered...
>
> And I have been to that
On Wednesday 08 May 2019 03:49:34 am Joe wrote:
> On Tue, 7 May 2019 18:47:50 -0400
>
> Gene Heskett wrote:
> > Greetings all;
> >
> > First it doesn't have a clue what to do with a wired network.
> > It sure wants to hook up to all the neighborhoods wifi, all of which
> > are secured.
> >
On 2019-05-08 08:55, Gene Heskett wrote:
That is a laborius process, taking at least 10x what any of my linux
machines need to reboot. From powerup to login was at least 15 minutes.
And I have been to that utility, but it has no place to disable ipv6 as
a
whole, has lots of names in the menu
On Wednesday 08 May 2019 02:16:29 am mick crane wrote:
> On 2019-05-07 23:47, Gene Heskett wrote:
> > Greetings all;
> >
> > First it doesn't have a clue what to do with a wired network.
> >
> >
> > Cheers, Gene (I need some winders help ) Heskett
>
>
On Tue, 7 May 2019 18:47:50 -0400
Gene Heskett wrote:
> Greetings all;
>
> First it doesn't have a clue what to do with a wired network.
> It sure wants to hook up to all the neighborhoods wifi, all of which
> are secured.
> Second, its like stretch seems locked to ipv6 but its ipv4 for at
>
On Wed, May 08, 2019 at 07:16:29AM +0100, mick crane wrote:
> On 2019-05-07 23:47, Gene Heskett wrote:
> >Greetings all;
> >
> >First it doesn't have a clue what to do with a wired network.
>
> >
> >Cheers, Gene (I need some winders help ) Heskett
>
>
On 2019-05-07 23:47, Gene Heskett wrote:
Greetings all;
First it doesn't have a clue what to do with a wired network.
Cheers, Gene (I need some winders help ) Heskett
usually bottom left corner click windows icon
click the settings that looks like a cog
select Ethernet / Change adapter
convince this brand new unibody HP to use a static wired
network setup?
In the FWIW category, it takes winders 10 about 10x longer to boot than
any of my linux machines. Makes me wonder if they should have named it
window-0.1 because it is boringly slow.
Cheers, Gene (I need some winders help
On Mon, 6 May 2019 15:16:09 -0500
David Wright wrote:
> On Mon 06 May 2019 at 10:56:47 (-0700), Patrick Bartek wrote:
> > On Mon, 6 May 2019 13:08:05 -0400 Greg Wooledge
> > wrote:
> > > On Mon, May 06, 2019 at 09:41:58AM -0700, Patrick Bartek wrote:
> > > > On Mon, 6 May 2019 10:24:24
On Mon 06 May 2019 at 10:56:47 (-0700), Patrick Bartek wrote:
> On Mon, 6 May 2019 13:08:05 -0400 Greg Wooledge wrote:
> > On Mon, May 06, 2019 at 09:41:58AM -0700, Patrick Bartek wrote:
> > > On Mon, 6 May 2019 10:24:24 -0400 Greg Wooledge
> > > wrote:
> > > > for dir in ab*/; do
> > > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg Wooledge wrote:
> [...]
> You said you had twenty-something directories named ab01, ab02, etc.
> So it should have matched unless you ran it from the wrong place,
> or unless you lied about your directory names.
>
> But nobody would EVER lie
On Mon, 6 May 2019 13:08:05 -0400
Greg Wooledge wrote:
> On Mon, May 06, 2019 at 09:41:58AM -0700, Patrick Bartek wrote:
> > On Mon, 6 May 2019 10:24:24 -0400
> > Greg Wooledge wrote:
> > > for dir in ab*/; do
> > > name=${dir%/}
> > > enfuse --output "$name.jpg" --compression=97
On Mon, May 06, 2019 at 09:41:58AM -0700, Patrick Bartek wrote:
> On Mon, 6 May 2019 10:24:24 -0400
> Greg Wooledge wrote:
> > for dir in ab*/; do
> > name=${dir%/}
> > enfuse --output "$name.jpg" --compression=97 "$dir"/*.jpg
> > done
>
> Typed in as a single line with a semi-colon at
On Mon, 6 May 2019 18:12:55 +0200
john doe wrote:
> On 5/6/2019 4:24 PM, Greg Wooledge wrote:
> > On Mon, May 06, 2019 at 06:57:00AM -0700, Patrick Bartek wrote:
> >> I want a script that allows commandline only applications that can't batch
> >> process to batch process. A speciifc example.
On Mon, 6 May 2019 10:24:24 -0400
Greg Wooledge wrote:
> On Mon, May 06, 2019 at 06:57:00AM -0700, Patrick Bartek wrote:
> > I want a script that allows commandline only applications that can't batch
> > process to batch process. A speciifc example. I will use the app
> > enfuse, an exposure
On 5/6/2019 4:24 PM, Greg Wooledge wrote:
> On Mon, May 06, 2019 at 06:57:00AM -0700, Patrick Bartek wrote:
>> I want a script that allows commandline only applications that can't batch
>> process to batch process. A speciifc example. I will use the app
>> enfuse, an exposure merging program, a
On Mon, May 06, 2019 at 06:57:00AM -0700, Patrick Bartek wrote:
> I want a script that allows commandline only applications that can't batch
> process to batch process. A speciifc example. I will use the app
> enfuse, an exposure merging program, a poor man's HDR.
>
> patrick@Debian9:~/Work$
On Sat, 4 May 2019 17:54:28 -0700
Will Mengarini wrote:
> * Patrick Bartek [19-05/04=Sa 08:08 -0700]:
> > [...] Perform an operation on files in unique, sequential
> > directories [...] never more than 99 -- usually a lot
> > less. The actual number will vary job to job. [...]
>
> If the
On Sat, 4 May 2019 15:34:16 -0500
Richard Owlett wrote:
> On 05/04/2019 10:08 AM, Patrick Bartek wrote:
> > Hi! All,
> >
> > Want to create a simple, one liner to type in to automate what I've
> > been doing manually: [*SNIP*]
>
> I think the critical question is,> *WHAT* do you wish to
On Sat, 4 May 2019 20:21:03 +0200
john doe wrote:
> On 5/4/2019 5:08 PM, Patrick Bartek wrote:
> > Hi! All,
> >
> > Want to create a simple, one liner to type in to automate what I've
> > been doing manually: Perform an operation on files in unique,
> > sequential directories, save the results
* Patrick Bartek [19-05/04=Sa 08:08 -0700]:
> [...] Perform an operation on files in unique, sequential
> directories [...] never more than 99 -- usually a lot
> less. The actual number will vary job to job. [...]
If the sequentially-numbered directories already exist:
`man find`
Else:
for
On 05/04/2019 10:08 AM, Patrick Bartek wrote:
Hi! All,
Want to create a simple, one liner to type in to automate what I've
been doing manually: [*SNIP*]
I think the critical question is,> *WHAT* do you wish to accomplish?
On 5/4/2019 5:08 PM, Patrick Bartek wrote:
> Hi! All,
>
> Want to create a simple, one liner to type in to automate what I've
> been doing manually: Perform an operation on files in unique,
> sequential directories, save the results of the operations for each
> directory with a file name of that
, but will remain constant for each job. Only the
numbers will sequence.
Any help is appreciated.
Thanks.
B
Lukkas Gabba wrote:
> First of all, sorry for my English, it's really bad. But let's get down to
> it, I need to talk to you urgently. If you can answer me quickly, thank
> you.
>
> $ dig example.com +noall +comments
>
> ; <<>> DiG 9.8.3-P1 <<>> example.com +noall +comments
> ;; global options:
First of all, sorry for my English, it's really bad. But let's get down to
it, I need to talk to you urgently. If you can answer me quickly, thank
you.
$ dig example.com +noall +comments
; <<>> DiG 9.8.3-P1 <<>> example.com +noall +comments
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<-
In-Reply-To: <3685896c-ded1-395b-6312-cef63a9d2...@pouzenc.fr>
>Ludovic Pouzenc
>I have doubts about the right package to submit against (gnome-shell,
>pulseaudio, wayland, udev, kernel)
>Poor work-around :
>
>- enable accessibility feature "visual-bell". The problem vanishes,
Since the
more than 400ms. On
debian 10, I didn't manage to strace gnome-shell without entire lock-up.
(suggestions are very welcome).
I think that system sound triggering should not freeze all input event
processing, in any case. It seems true with gnome session over Xorg, it
seems false to me with gnome
On Tue, Apr 16, 2019 at 04:39:32PM +0200, Peter Wiersig wrote:
>rss RSS resident set size, the non-swapped physical
> memory that a task has used (in kiloBytes).
> (alias rssize, rsz).
> ...
>vsz VSZ virtual memory size of
On Wed, Apr 17, 2019 at 01:14:36AM +0200, Peter Wiersig wrote:
> Reco writes:
>
> Hi Reco,
>
> > On Tue, Apr 16, 2019 at 04:39:32PM +0200, Peter Wiersig wrote:
> >> VSZ is the Virtual Memory Size. (...),
> >>including memory that is swapped out,
> >> memory that is allocated, but not used,
>
Martin Schwarz writes:
>
> Here's the output from some commands I hope to be helpful:
>
> The machine in this example is a RADIUS server but has not even gone
> productive ... no incoming client requests yet. (But the problem is not
> related to the RADIUS server software - OSC Radiator - since
Reco writes:
Hi Reco,
> On Tue, Apr 16, 2019 at 04:39:32PM +0200, Peter Wiersig wrote:
>> VSZ is the Virtual Memory Size. (...),
>>including memory that is swapped out,
>> memory that is allocated, but not used,
>> and memory that is from shared
Hi.
On Tue, Apr 16, 2019 at 04:39:32PM +0200, Peter Wiersig wrote:
> VSZ is the Virtual Memory Size. It includes all memory that the process
> can access, including memory that is swapped out, memory that is
> allocated, but not used, and memory that is from shared libraries.""
Given
Martin Schwarz writes:
> root@rad-m2m-srv02:~# ps aux --sort=-rss | head -15
you're choosing the wrong sort field to debug your problem here:
man ps:
"""
rss RSS resident set size, the non-swapped physical memory
that a task has used (in kiloBytes).
Hi.
On Tue, Apr 16, 2019 at 02:30:57PM +0200, Martin Schwarz wrote:
> > slabtop from "procps" package, definitely.
> > Should've thought of it earlier.
>
> I did take a look at slaptop (and at /proc/slabinfo) before. But since the
> values for "SReclaimable" and "SUnreclaim" from
nload modules that are in use, of course. Unloading
> > vmw_balloon, vmw_vmci, and vmw_vsock_vmci_transport didn't help.
>
> I doubt that these are the problem. Unless you're changing VM's RAM at
> runtime (and you wrote you don't).
We sometimes do increase a VM's RAM while
l in C.
> Only I can't unload modules that are in use, of course. Unloading
> vmw_balloon, vmw_vmci, and vmw_vsock_vmci_transport didn't help.
I doubt that these are the problem. Unless you're changing VM's RAM at
runtime (and you wrote you don't).
If you can unload it - it's not used, henc
use, of
course. Unloading vmw_balloon, vmw_vmci, and vmw_vsock_vmci_transport
didn't help.
> And that means - 'perf top', or better yet - 'perf record'.
I have never used perf before, will look into it.
Thanks a lot for your insight!
Martin
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
Hi.
On Mon, Apr 15, 2019 at 04:40:56PM +0200, Martin Schwarz wrote:
> The system from my previous example has already been rebooted, sorry!
Kind of expected. It's useful nevertheless.
> But here's from another system that currently starts showing the same
> problem and has an equally
801 - 900 of 20720 matches
Mail list logo
