On Sat, Apr 14, 2012 at 11:24 PM, antonio montagnani
wrote:
> Tommy Pham ha scritto / said the following il giorno/on 15/04/2012 01:13:
>>
>> On Sat, Apr 14, 2012 at 1:54 PM, antonio montagnani
>> wrote:
>>>
>>> Installed F16 on a quite old laptop (Acer 5672WLMI) of a friend of mine
>>> repla
Tommy Pham ha scritto / said the followingil giorno/on 15/04/2012 01:13:
On Sat, Apr 14, 2012 at 1:54 PM, antonio montagnani
wrote:
Installed F16 on a quite old laptop (Acer 5672WLMI) of a friend of mine
replacing WinXp: everything is o.k., Fedora is running smoothly, the only
problem is t
> Definitely yes. But again, that only matters if you had lots of curl
> commands each with its own >> file open. But your code had one >> open
> and lots of echoes (well, curls) using it.
>
> Which is it? (Actually, both should work. But we need to know what is
> actually goging on.)
It's the l
>
> if your script forks off lots of curls into a file and does not wait for
> them all, then you may get to run the grep before they all finish, hence
> the weird results.
If ioTest.sh is the original example I posted, I'm NOT doing this:
./ioTest.sh | grep ^A | wc -l
I am doing this:
./ioTes
On Sat, 2012-04-14 at 20:26 +0200, Reindl Harald wrote:
>
> Am 14.04.2012 20:19, schrieb Patrick O'Callaghan:
> >> When you do a "kill" you are sending a "signal" to a process and that
> >> process will
> >> act upon it depending on the signal. For example, if you did a "kill -1"
> >> to the
>
On 04/15/2012 10:36 AM, Amadeus W.M. wrote:
> It does seem to work, but can you explain why it does? Would it still
> work if each process outputs, say, 1Mb? 100Mb?
It works fine when i is set to 100.
I think I'll leave the explanations to Cameron, who is doing a *much* better
job in
that
On 15Apr2012 02:36, Amadeus W.M. wrote:
| > [egreshko@meimei test]$ mkfifo pipe
| > [egreshko@meimei test]$ ./io.sh > pipe
| > [egreshko@meimei test]$ cat pipe | grep ^A | wc
| > 100 100 600
| >
|
| It does seem to work, but can you explain why it does? Would it still
| work if each
On 15Apr2012 02:32, Amadeus W.M. wrote:
| > | Multiple processes that open the same file for writing each maintain |
| > their own file positions, so they may overwrite the output of another |
| > process, unless the processes all open the file with the "O_APPEND" |
| > option.
| >
| > This only
>
> [egreshko@meimei test]$ mkfifo pipe
> [egreshko@meimei test]$ ./io.sh > pipe
>
> [egreshko@meimei test]$ cat pipe | grep ^A | wc
> 100 100 600
>
It does seem to work, but can you explain why it does? Would it still
work if each process outputs, say, 1Mb? 100Mb?
--
users mail
>
> | Multiple processes that open the same file for writing each maintain |
> their own file positions, so they may overwrite the output of another |
> process, unless the processes all open the file with the "O_APPEND" |
> option.
>
> This only matters if the processes _independently_ opened t
On Sat, 14 Apr 2012 09:45:50 -0700, John Wendel wrote:
> On 04/14/2012 08:20 AM, Amadeus W.M. wrote:
>>> If you really would like to get output in sequence, write to a pipe,
>>> and have a reader process drain the pipe to a logfile. It's pretty
>>> easy; look at "mknod" with the 'p' option, or "m
On Sat, Apr 14, 2012 at 1:54 PM, antonio montagnani
wrote:
> Installed F16 on a quite old laptop (Acer 5672WLMI) of a friend of mine
> replacing WinXp: everything is o.k., Fedora is running smoothly, the only
> problem is that the webcam is not recognized, also lsusb doesn't show
> anything.
> I g
On 14Apr2012 09:45, John Wendel wrote:
| > I don't see how echoing into a pipe would change the problem.
| > Theoretically, if several processes (e.g. echo) are running in the
| > background, e.g. on a round robin basis, then potentially I could see
| > random sequences of As, Bs and Cs. It doesn'
On 14 Apr 2012 at 9:45, John Wendel wrote:
Date sent: Sat, 14 Apr 2012 09:45:50 -0700
From: John Wendel
To: users@lists.fedoraproject.org
Subject:Re: off topic: combined output of concurrent
processes
> On 04/14/2012 08:20 AM,
Installed F16 on a quite old laptop (Acer 5672WLMI) of a friend of mine
replacing WinXp: everything is o.k., Fedora is running smoothly, the
only problem is that the webcam is not recognized, also lsusb doesn't
show anything.
I guess that webcam is a Logitech Orbicam, from the specification, als
On 04/14/2012 04:11 PM, Alan Cox wrote:
Under what circumstance would killing a waiting process
be worse than a process that should have waited,
but terminated instead?
When it leaves the system in an unstable state or where corruption could
follow. Far better then to leave that process stuck un
> One of my favorite near infinite hangs is a giant process that
> decides to core dump across NFS. I don't know if it is still
> the case, but once upon a time when linux started writing
> a core file, it would never stop for any reason till it was
> done.
We fixed that one 8)
Alan
--
users mai
On Sat, 14 Apr 2012 21:11:36 +0100
Alan Cox wrote:
> In the case of NFS btw read the mount page for the "soft" and "intr"
> options and also read about umount -f.
One of my favorite near infinite hangs is a giant process that
decides to core dump across NFS. I don't know if it is still
the case,
> Under what circumstance would killing a waiting process
> be worse than a process that should have waited,
> but terminated instead?
When it leaves the system in an unstable state or where corruption could
follow. Far better then to leave that process stuck unless things sort
out.
In the case o
On 14 April 2012 20:37, jdow wrote:
> I was about to comment a little more acerbicly that he's obviously a
> youngster.
> Killing power used to be the only way to shut down a locked up computer
> with
> ANY then available OS on it. I remember those bad old days too well.
>
> {^_-}
Shudder. I
On 04/14/2012 12:40 PM, jdow wrote:
As long as that is enabled in the BIOS it will perform a hard
shutdown. Of course, if the heart is racing sometimes it is wise to tell
the
poor victim, hold it in for 30 seconds or until the computer shuts down.
Back when I was on the phone, you sometimes nee
On 14 April 2012 20:25, Michael Hennebry wrote:
>
> Under what circumstance would killing a waiting process
> be worse than a process that should have waited,
> but terminated instead?
>
>
Waiting for a timeout implies a reasonably sane state of affairs regarding
any data in transit, and if the wo
On 14 April 2012 20:06, Joe Zeff wrote:
> I'd think that there'd have to be a special command, requiring root, to do
> it for exactly that reason. There's no way you can safely automate that
> decision, and it's probably best if the average user doesn't have direct
> access to it; if nothing els
On 04/14/2012 12:25 PM, Michael Hennebry wrote:
Under what circumstance would killing a waiting process
be worse than a process that should have waited,
but terminated instead?
I think that the idea is that if the process is in an uninterruptable
sleep, it's for a good reason and the kernel is
On 2012/04/14 12:37, Joe Zeff wrote:
On 04/14/2012 12:13 PM, My Usenet wrote:
Typically if you need to do a bios reset - then unplugging the battery
will be helpful.
I take it that you didn't bother to read my original post. I was talking about a
computer hanging while processing an interrupt
On 2012/04/14 12:30, Joe Zeff wrote:
On 04/14/2012 12:07 PM, Reindl Harald wrote:
every computer i know does a hard power-off pressing the power-button
for 5 seconds if all other things are failing
This was about ten or twelve years ago. I'm not sure, but I might have even had
them try that. (
On 04/14/2012 12:13 PM, My Usenet wrote:
Typically if you need to do a bios reset - then unplugging the battery
will be helpful.
I take it that you didn't bother to read my original post. I was
talking about a computer hanging while processing an interrupt with
interrupts disabled. Not some
On 04/14/2012 12:07 PM, Reindl Harald wrote:
every computer i know does a hard power-off pressing the power-button
for 5 seconds if all other things are failing
This was about ten or twelve years ago. I'm not sure, but I might have
even had them try that. (Please note that even then, their l
On Sat, 14 Apr 2012, Andy Blanchard wrote:
On 14 April 2012 19:26, Reindl Harald wrote:
on the other hand i am missing understanding that there
is no root-command to kill such processes without
"their help"
the kernel should be able to kill anything
sounds like a missing interface for me
On 04/14/2012 01:07 PM, Reindl Harald wrote:
>
> Am 14.04.2012 20:55, schrieb Joe Zeff:
>> Once, the computer was a laptop and the caller had to go hunt up a
>> screwdriver to take the battery out.
> not really
>
> every computer i know does a hard power-off pressing the power-button
> for 5 secon
Am 14.04.2012 20:55, schrieb Joe Zeff:
> Once, the computer was a laptop and the caller had to go hunt up a
> screwdriver to take the battery out.
not really
every computer i know does a hard power-off pressing the power-button
for 5 seconds if all other things are failing
signature.asc
Des
On 04/14/2012 11:42 AM, Andy Blanchard wrote:
In theory, yes, but the problem would be that the kernel would no longer
have any way of knowing what state the device being waited on is in.
Depending on the device that could be very bad news and potentially
result in trashed data.
I'd think that
On 04/14/2012 11:19 AM, Patrick O'Callaghan wrote:
Exactly. The correct view of "kill -9" is not that you kill the process
but that you order the process to commit suicide. If it's not listening,
no amount of shouting is going to make a difference.
As another example, your CPU sometimes disable
On Sat, 14 Apr 2012 18:30:37 +0200
suvayu ali wrote:
> > Also try booting to an older kernel (from before the problem), if
> > you have one.
> >
>
> I had tried this with no success. If it was a driver issue booting to
> a kernel from before the problem started should have worked, but it
> didn
On 14 April 2012 19:26, Reindl Harald wrote:
>
> on the other hand i am missing understanding that there
> is no root-command to kill such processes without
> "their help"
>
> the kernel should be able to kill anything
> sounds like a missing interface for me
>
In theory, yes, but the problem wo
Am 14.04.2012 20:19, schrieb Patrick O'Callaghan:
>> When you do a "kill" you are sending a "signal" to a process and that
>> process will
>> act upon it depending on the signal. For example, if you did a "kill -1" to
>> the
>> named process it will cause it to reread its configuration files a
On Sat, 2012-04-14 at 23:14 +0800, Ed Greshko wrote:
> On 04/14/2012 10:54 PM, Hal wrote:
> >
> >
> > On 4/14/2012 8:08 AM, suvayu ali wrote:
> >> On Fri, Apr 13, 2012 at 21:09, Andrew Gray wrote:
> >>> Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
> >> I'll repeat myself: "The only way
On 04/14/2012 08:20 AM, Amadeus W.M. wrote:
If you really would like to get output in sequence, write to a pipe, and
have a reader process drain the pipe to a logfile. It's pretty easy;
look at "mknod" with the 'p' option, or "mkfifo". I'd still suggest
tagging each output line with an identifi
Hey Stan,
I found something interesting, comments are below.
On Sat, Apr 14, 2012 at 17:06, stan wrote:
>
> This is a long shot, but it might be that alsa has sorted your sound
> devices in a different order on boot. It sounds like it thinks your
> acpi might be a sound device.
>
> Try
> aplay
On 04/14/2012 11:20 PM, Amadeus W.M. wrote:
> Theoretically, if several processes (e.g. echo) are running in the
> background, e.g. on a round robin basis, then potentially I could see
> random sequences of As, Bs and Cs. It doesn't seem to be the case in
> practice though. So which is it?
Oh,
On 04/14/2012 11:20 PM, Amadeus W.M. wrote:
> For the sake of the argument, assume I echo 500 As, 500 Bs and 500 Cs.
>
> I don't care which process the output is coming from. It doesn't matter
> which order the As, Bs and Cs are output. All I care about is that I
> don't get 349As followed by 24
On 04/14/2012 11:22 PM, Hal wrote:
> FINE..then REBOOT the darn thing and quit wasting time ..!!
Actually, the only time wasted was yours in answering a question erroneously.
I view correcting your response as a community service. :-) :-)
--
Never be afraid to laugh at yourself, after all, yo
On 4/14/2012 11:15 AM, suvayu ali wrote:
Hi Hal,
On Sat, Apr 14, 2012 at 16:54, Hal wrote:
On 4/14/2012 8:08 AM, suvayu ali wrote:
On Fri, Apr 13, 2012 at 21:09, Andrew Gray
wrote:
Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
I'll repeat myself: "The only way to get rid of t
> If you really would like to get output in sequence, write to a pipe, and
> have a reader process drain the pipe to a logfile. It's pretty easy;
> look at "mknod" with the 'p' option, or "mkfifo". I'd still suggest
> tagging each output line with an identifier and sequence number.
>
For the sa
Hi Hal,
On Sat, Apr 14, 2012 at 16:54, Hal wrote:
> On 4/14/2012 8:08 AM, suvayu ali wrote:
>>
>> On Fri, Apr 13, 2012 at 21:09, Andrew Gray
>> wrote:
>>>
>>> Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
>>
>> I'll repeat myself: "The only way to get rid of these processes is to
>> w
On 04/14/2012 10:54 PM, Hal wrote:
>
>
> On 4/14/2012 8:08 AM, suvayu ali wrote:
>> On Fri, Apr 13, 2012 at 21:09, Andrew Gray wrote:
>>> Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
>> I'll repeat myself: "The only way to get rid of these processes is to
>> wait or reboot."
>>
>
> Par
On Sat, 14 Apr 2012 14:47:49 +0200
suvayu ali wrote:
> I looked in /var/log/messages. I see no suspicious messages. But I do
> see the following:
>
> pulseaudio[1455]: module-alsa-card.c: Failed to find a working
> profile. pulseaudio[1455]: module.c: Failed to load module
> "module-alsa-card"
On 4/14/2012 8:08 AM, suvayu ali wrote:
On Fri, Apr 13, 2012 at 21:09, Andrew Gray wrote:
Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
I'll repeat myself: "The only way to get rid of these processes is to
wait or reboot."
Pardon my stupidity, if you can observe ot determine th
On Fri, Apr 13, 2012 at 10:31 PM, Amadeus W.M. wrote:
>>
>> [egreshko@meimei test]$ grep ^A out | wc
>> 97 97 582
>> [egreshko@meimei test]$ grep ^B out | wc
>> 94 94 564
>> [egreshko@meimei test]$ grep ^C out | wc
>> 96 96 576
>
> I replicated this and in
On Sat, 14 Apr 2012 15:15:44 +0200
suvayu ali wrote:
> On Sat, Apr 14, 2012 at 14:47, suvayu ali
> wrote:
> >> I don't think this is an alsa issue. If alsamixer sees the mic,
> >> then alsa is handling it properly, if the driver and hardware are
> >> OK.
> >>
> >> Install pavucontrol and check
On 04/14/2012 10:09 PM, Dave Ihnat wrote:
> On Sat, Apr 14, 2012 at 09:49:00PM +0800, Ed Greshko wrote:
>> The one problem would be if, as the OP's script is written,
>> backgrounding of processes is done there is no way to control the
>> order of data being written to the pipe. And, as you pointe
On Sat, Apr 14, 2012 at 09:49:00PM +0800, Ed Greshko wrote:
> The one problem would be if, as the OP's script is written,
> backgrounding of processes is done there is no way to control the
> order of data being written to the pipe. And, as you pointed out,
> you may want to write out sequence num
On Sat, Apr 14, 2012 at 11:01, Aaron Konstam wrote:
> Although evince will do
> that, acroread is the adobe reader application.
You missed the point I was trying to make, completely.
Please, re-read my message. It has been answered already anyway.
But thanks for your response.
FC
--
During tim
On Fri, 2012-04-13 at 17:56 -0300, Fernando Cassia wrote:
> I found myself on a command line window, wanting to open a PDF, and I
> didnt remember the name of the pdf reader that now comes as a default
> install for Fedora. Too many years of "just installing Acrobat" left
> me with "./acroread wha
On Sun, 2012-04-08 at 12:34 +0100, John Austin wrote:
> On Sat, 2012-03-31 at 19:09 +0100, James Wilkinson wrote:
> > I asked Patrick:
> > > Does it work with older (pre 3.3) kernels?
> >
> > Patrick Lists wrote:
> > > I don't have a pre-3.3 kernel as these are kickstart deployments of
> > > F16 +
On 04/14/2012 09:33 PM, Dave Ihnat wrote:
> On Sat, Apr 14, 2012 at 01:35:38AM +, Amadeus W.M. wrote:
>> So here is the question. Suppose I have several processes that run
>> concurrently and each outputs stuff to stdout. Can the combined output be
>> intermingled?
> If you just send the out
On Sat, Apr 14, 2012 at 03:30, Ed Greshko wrote:
> Why don't you switch your youtube experience to hmtl5?
>
> http://www.youtube.com/html5
Just to parachute into this thread, and not being the OP...
I found the default plug-in to be lacking. Particularly, it displays
some youtube videos, but not
On 04/14/2012 09:11 PM, Joel Rees wrote:
> With the old flash plugin, youtube works fine.
>
>> > May put
>> > flash in one account on the box I'm using here, to see if it's perhaps
>> > a CPU or other hardware issue but not now.
> Okay, the current flash plugin and yesterdays both work on this box.
On Sat, Apr 14, 2012 at 01:35:38AM +, Amadeus W.M. wrote:
> So here is the question. Suppose I have several processes that run
> concurrently and each outputs stuff to stdout. Can the combined output be
> intermingled?
If you just send the output to a file, you've no way of knowing exactly
Joel Rees writes:
Well, I just downloaded the tarball once more, and took a look. cmp
Why are you making this more difficult than it needs to me?
Just install their yum repository package, and you get your Flash updates
via Packagekit.
This morning PackageKit prompted me to update the ker
On Sat, Apr 14, 2012 at 14:47, suvayu ali wrote:
>> I don't think this is an alsa issue. If alsamixer sees the mic, then
>> alsa is handling it properly, if the driver and hardware are OK.
>>
>> Install pavucontrol and check how pulse is viewing the microphone.
>> Perhaps it inadvertently got tur
On Sat, Apr 14, 2012 at 03:15, Joel Rees wrote:
> Well, I just downloaded the tarball once more, and took a look. cmp
> says today's tarball is different from yesterdays.
I thought Adobe had dropped Linux support for Flash, expect in its
"embedded into Chrome" version?
FC
--
During times of Un
On Sat, Apr 14, 2012 at 5:08 PM, Joel Rees wrote:
> On Sat, Apr 14, 2012 at 3:30 PM, Ed Greshko wrote:
>> On 04/14/2012 02:15 PM, Joel Rees wrote:
>>> Well, I just downloaded the tarball once more, and took a look. cmp
>>> says today's tarball is different from yesterdays. Unpacking the
>>> tarba
Hi Stan,
Thanks for your helpful comments.
On Fri, Apr 13, 2012 at 18:33, stan wrote:
> Did anything change around the time the mic stopped working?
>
I think I inadvertently dropped my backpack to the floor (from about 15
cm) with the ThinkPad inside along with a few books and some clothes. I
On Fri, Apr 13, 2012 at 21:09, Andrew Gray wrote:
> Again how do you kill a cp in UNINTERRUPTIBLE SLEEP !!!
I'll repeat myself: "The only way to get rid of these processes is to
wait or reboot."
--
Suvayu
Open source is the future. It sets us free.
--
users mailing list
users@lists.fedorapro
Am 14.04.2012 13:43, schrieb Antonio.montagnani:
> I was suggesting that if either the browser or
> the server does not know how to play nice,
> the user might want to make a firm suggestion.
> I've occasionally been annoyed by a text, not .txt,
> file mime-typed application/binary or some such.
Inviato da Samsung Mobile
Original message
Subject: Re: Perhaps this exists already, and if not, it should...
From: Michael Hennebry
To: Community support for Fedora users
CC:
On Sat, 14 Apr 2012, Reindl Harald wrote:
> Am 14.04.2012 00:07, schrieb Michael Hennebry:
>
clamav-server installed using:
https://raw.github.com/csmart/naa/master/sysadmin/scripts/configure-clamd.sh
Am running clamd instance as user "clamav"
How can I get
the following to work as clamav,
or do I have to get user clamav
to join a privileged group?
--snips from freshclam.conf
#
On Sat, Apr 14, 2012 at 3:30 PM, Ed Greshko wrote:
> On 04/14/2012 02:15 PM, Joel Rees wrote:
>> Well, I just downloaded the tarball once more, and took a look. cmp
>> says today's tarball is different from yesterdays. Unpacking the
>> tarball and doing a diff -r reveals that they differ in the co
69 matches
Mail list logo