On 28 Aug 2023 21:26, Mario Marietto wrote:
Anyway,I found it relevant that I have the error with the wi-fi driver in
debian,but not with devuan.
On Mon, Aug 28, 2023 at 9:19 PM Mario Marietto
wrote:
Yes.thanks. I've already asked there. The author is busy with different
projects,so I tried t
Anyway,I found it relevant that I have the error with the wi-fi driver in
debian,but not with devuan.
On Mon, Aug 28, 2023 at 9:19 PM Mario Marietto
wrote:
> Yes.thanks. I've already asked there. The author is busy with different
> projects,so I tried to look for some help from different sources
Yes.thanks. I've already asked there. The author is busy with different
projects,so I tried to look for some help from different sources or the
thing will take too long a time.
On Mon, Aug 28, 2023 at 8:40 PM zithro wrote:
> On 28 Aug 2023 19:00, Christian Britz wrote:
> > On 28.08.23, 18:44, zi
Sure. It's debian. Uname -a for me is different because I have recompiled
the kernel several times. And I can't use 6 on this old netbook if I want
to enable kvm. The latest version supported is 5.7. Higher than this qemu
will not be recognized by kvm anymore. No problem if you don't want to use
kv
On 28 Aug 2023 19:00, Christian Britz wrote:
On 28.08.23, 18:44, zithro wrote:
On 27 Aug 2023 12:09, Mario Marietto wrote:
$ uname -a
Linux chromarietto 5.4.244-stb-cbe
#8 SMP PREEMPT Sat Aug 19 22:19:32 UTC 2023 armv7l GNU/Linux
Is it normal to get this "old" kernel on bookworm ARM ? No 6.x
On 28.08.23, 18:44, zithro wrote:
> On 27 Aug 2023 12:09, Mario Marietto wrote:
>> $ uname -a
>> Linux chromarietto 5.4.244-stb-cbe
>> #8 SMP PREEMPT Sat Aug 19 22:19:32 UTC 2023 armv7l GNU/Linux
>
> Is it normal to get this "old" kernel on bookworm ARM ? No 6.x versions ?
This does not seem to b
On 27 Aug 2023 12:09, Mario Marietto wrote:
Hello.
I'm running Debian bookworm on my ARM Chromebook,model "xe303c12" and I've
recompiled the kernel to enable KVM,so now my system sounds like this :
If you are going to use libvirt, you could also try Xen (via packages),
but I don't know if you
--system libvirt-qemu
$ sudo newgrp libvirt-qemu
$ newgrp libvirt
$ /usr/local/sbin# libvirtd &
[1] 2875
$ /usr/local/sbin# virtqemud &
info : libvirt version: 9.7.0 info :
hostname: chromarietto error : virPidFileAcquirePathFull:409
Failed to acquire pid file : /var/local/run/libvirt/qe
André Rodier wrote:
> Hi,
>
> With iptables, I was able to use the match extension, and create rules per
> program or pid, for isntance:
>
> iptables -A OUTPUT --match owner -p tcp --cmd-owner tinyproxy -j ACCEPT
> iptables -A OUTPUT --match owner -p tcp --pid-owner 4554 -
Hi,
With iptables, I was able to use the match extension, and create rules
per program or pid, for isntance:
iptables -A OUTPUT --match owner -p tcp --cmd-owner tinyproxy -j ACCEPT
iptables -A OUTPUT --match owner -p tcp --pid-owner 4554 -j ACCEPT
How can I achieve the same, on Linux, using
> > # while true; do kill -ILL 1 ; echo -n "." ; sleep 0.5 ; done
> >
> > I found out PID 1 is killed when I tried to reboot:
> > # reboot
> > Failed to open /dev/initctl: No such device or address
> > Failed to talk to init daemon.
> >
On Sat, May 25, 2019 at 08:35:45AM -0400, Kenneth Parker wrote:
[...]
> Can somebody, please link me to the Documentation Files on those SysReq
> keys? Thanks!
https://en.wikipedia.org/wiki/Magic_SysRq_key
Cheers
-- t
signature.asc
Description: Digital signature
e brought down by sending
> > > > SIGILL to Systemd
> > > > Date: Fri, 24 May 2019 22:04:34 +0200
> > > > From: Martin Steigerwald
> > > > To: DNG
> > > >
> > > >
> > > >
> > > > Hi!
>
:04:34 +0200
> > > From: Martin Steigerwald
> > > To: DNG
> > >
> > >
> > >
> > > Hi!
> > >
> > > Today in a Linux training a participant attempted to bring down
> > > Debian workstation with Systemd by sending signals t
I've noticed this message about once per day just after midnight.
Googling about it did not seem (to me) to produce anything definitive,
but perhaps I did not try hard enough.
Does anybody here know
1. why this is being printed to the system log
2. whether I should just tell logcheck to ignore it
On 10/11/2016 08:04 PM, Pol Hallen wrote:
> Hi all, after upgraded oldstable to stable it happens that systemd
> doesn't create PID file of these packages:
>
> openvpn
> smartmontools
There's a general misconception here: systemd never creates pid
files for daemons.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 25, 2015 at 04:27:10PM +, Simon wrote:
Hi All,
Using Debian 8 and I'd like to run rsnapshot as a regular (non-root)
user but it doesn't have permissions to drop the pid file in
/var/run.
I created a directory called rs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 25, 2015 at 04:27:10PM +, Simon wrote:
> Hi All,
>
> Using Debian 8 and I'd like to run rsnapshot as a regular (non-root)
> user but it doesn't have permissions to drop the pid file in
> /var/run.
>
&g
Hi All,
Using Debian 8 and I'd like to run rsnapshot as a regular (non-root)
user but it doesn't have permissions to drop the pid file in /var/run.
I created a directory called rsnapshot in /var/run with the appropriate
permissions which, I thought, fixed the problem. Unfortunat
On Lu, 04 aug 14, 23:12:41, The Wanderer wrote:
>
> However, I'm using radeon (or related non-proprietary driver) on a
> different system, and I still get the same 80x25 behavior. I do notice
> an error message about being unable to load fglrx on that system, so
> possibly it's still listed in som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/04/2014 04:44 PM, Andrei POPESCU wrote:
> On Lu, 04 aug 14, 11:20:38, Bob Proulx wrote:
>
>> Or it is also possible that the hardware differences is the source
>> of the difference. Your graphics display hardware may decide to
>> use the 25
On Lu, 04 aug 14, 11:20:38, Bob Proulx wrote:
>
> Or it is also possible that the hardware differences is the source of
> the difference. Your graphics display hardware may decide to use the
> 25 line terminal while mine chooses a 48 line terminal.
I'm guessing it's due to fglrx, which is blackl
Am 04.08.2014 20:14, schrieb Rob Owens:
> You could try installing bootlogd. I just tried it on my jessie system
> (running systemd) and it didn't log anything. But I recall using it on
> Wheezy and I think it logged all the services starting/stopping/failing.
Don't use bootlogd. That's a hack
- Original Message -
> From: "Mark Carroll"
>
> Curt writes:
>
> > On 2014-07-25, Brian wrote:
> >>
> >> With sysvinit the default at booting is for the screen messages to fly
> >> past at a bewildering speed and then for the screen to be cleared by
> >> agetty. Nobody particularily
The Wanderer wrote:
> Maybe it's got something to do with the way I install Debian? I don't
> quite follow the normal installer defaults 100%; I do partitioning
> manually, and I disable all tasks except for the base system, then
> install everything I need (including X) separately afterwards.
I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 10:27 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Bob Proulx wrote:
>>> I must have a higher resolution monitor than you. (shrug) I have
>>> 44 lines of console boot messages. The monitor is an older
>>> 1280x1024 monitor. Th
The Wanderer wrote:
> Bob Proulx wrote:
> > I must have a higher resolution monitor than you. (shrug) I have 44
> > lines of console boot messages. The monitor is an older 1280x1024
> > monitor. The default console size is 48 lines and annoyingly doesn't
> > use the bottom third of the screen.
Hi Tom,
Tom H wrote:
> Bob Proulx wrote:
> > kill -1 1 # Tell init to re-read the inittab file.
>
> You can use "telinit q" instead of "kill -1 1".
It is the same thing. Six of one or a half dozen of the other. Use
whichever one you prefer. I prefer sending SIGHUP. Among other
thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 04:50 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Bob Proulx wrote:
>>> Note that Squeeze 6 /sbin/getting does not support --noclear so
>>> don't set this on Squeeze systems. But for Wheezy 7 and later
>>> this snippet will mak
On Sun, Aug 3, 2014 at 2:12 PM, Bob Proulx wrote:
>
> if [ -f /etc/inittab ]; then
> if grep -q '^1:2345:respawn:/sbin/getty 38400 tty' /etc/inittab; then
> log "Fixing getty --noclear in /etc/inittab"
> sed --in-place '/^1/s/getty 38400/getty --noclear 38400/' /etc/initt
The Wanderer wrote:
> Bob Proulx wrote:
> > The Wanderer wrote:
> >> Where do you set this, exactly? /etc/inittab ?
> >
> > Note that Squeeze 6 /sbin/getting does not support --noclear so don't
> > set this on Squeeze systems. But for Wheezy 7 and later this
> > snippet will make automate the cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/03/2014 02:12 PM, Bob Proulx wrote:
> The Wanderer wrote:
>
>> Brian wrote:
>>> Upstream for agetty responded to concerns about security from
>>> users, some of whom apparently had the compliance police
>>> breathing down their necks. My vie
The Wanderer wrote:
> Brian wrote:
> > Bob Proulx wrote:
> >> Just for the record I complain about that behavior. I don't like
> >> the fancy tty colors and always disable them. I don't like the
> >> screen clearing those away and so I always set the getty --noclear
> >> option. The problem is th
On Sun 03 Aug 2014 at 12:39:50 +1000, Zenaan Harkness wrote:
> On 8/3/14, Brian wrote:
> >
> > Upstream for agetty responded to concerns about security from users,
> > some of whom apparently had the compliance police breathing down their
> > necks. My view on such idiocy is probably not for this
On 2014-08-03 09:16 +0200, Tom H wrote:
> On Sat, Aug 2, 2014 at 8:53 PM, The Wanderer wrote:
>> On 08/02/2014 03:15 PM, Brian wrote:
>>> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
Brian wrote:
>
> With sysvinit the default at booting is for the screen messages
> to
On Sat, Aug 2, 2014 at 8:53 PM, The Wanderer wrote:
> On 08/02/2014 03:15 PM, Brian wrote:
>> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>>> Brian wrote:
With sysvinit the default at booting is for the screen messages
to fly past at a bewildering speed and then for the
On 8/3/14, Brian wrote:
> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>> Brian wrote:
>> > With sysvinit the default at booting is for the screen messages to fly
>> > past at a bewildering speed and then for the screen to be cleared by
>> > agetty. Nobody particularily complains about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/02/2014 03:15 PM, Brian wrote:
> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>
>> Brian wrote:
>
>>> With sysvinit the default at booting is for the screen messages
>>> to fly past at a bewildering speed and then for the screen t
On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
> Brian wrote:
> > With sysvinit the default at booting is for the screen messages to fly
> > past at a bewildering speed and then for the screen to be cleared by
> > agetty. Nobody particularily complains about this behaviour. Unless
> > you
Brian wrote:
> With sysvinit the default at booting is for the screen messages to fly
> past at a bewildering speed and then for the screen to be cleared by
> agetty. Nobody particularily complains about this behaviour. Unless
> you have an excellent visual memory you are in the dark as regards wha
On Mon, Jul 28, 2014 at 11:52:51PM +0300, Andrei POPESCU wrote:
> On Lu, 28 iul 14, 08:41:39, Chris Bannister wrote:
> > On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> > >
> > > You are aware of course that:
> > > - it's also possible to scroll *back* (surprise, surprise)
> >
>
On Lu, 28 iul 14, 08:41:39, Chris Bannister wrote:
> On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> >
> > You are aware of course that:
> > - it's also possible to scroll *back* (surprise, surprise)
>
> Can you still? It used to be , (which didn't work last
> time I tried) have
On Lu, 28 iul 14, 11:22:30, Zenaan Harkness wrote:
>
> 3) disable scrolling (I think Andrei said this is possible),
No, I said stopped (Ctrl-S / Ctrl-Q).
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth
On 7/28/14, Chris Bannister wrote:
> On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
>> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
>> > I've thought for years, and noted in my "fix unix" notes that
>> > boot messages ought be written starting at the top of the
>> > screen,
On Sun, Jul 27, 2014 at 11:20:13AM +0300, Andrei POPESCU wrote:
> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
> > I've thought for years, and noted in my "fix unix" notes that
> > boot messages ought be written starting at the top of the
> > screen, then when they get to the bottom, rather t
On Du, 27 iul 14, 09:59:21, Mark Carroll wrote:
>
> This is the problem with what the current wheezy default seems to be of
> the screen clearing when the login prompt is reached. Before agetty
> started doing that, I could usefully scroll back, now it seems to wipe
> out anything much after check
Andrei POPESCU writes:
> On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
>> On 7/26/14, Brian wrote:
>>
>> > With sysvinit the default at booting is for the screen messages to fly
>> > past at a bewildering speed and then for the screen to be cleared by
>> > agetty.
>>
>> I've thought for y
On Du, 27 iul 14, 12:34:17, Zenaan Harkness wrote:
> On 7/26/14, Brian wrote:
>
> > With sysvinit the default at booting is for the screen messages to fly
> > past at a bewildering speed and then for the screen to be cleared by
> > agetty.
>
> I've thought for years, and noted in my "fix unix" n
On 7/26/14, Brian wrote:
> On Fri 25 Jul 2014 at 16:02:18 -0400, The Wanderer wrote:
>> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>> > Hi,
>> > Am 25.07.2014 20:27, schrieb Steven Post:
>> >> I'm running Jessie (lagging about 5 days behind with the updates)
>> >> and use systemd-sysv. Today I n
On Sun, 27 Jul 2014, Michael Biebl wrote:
> Am 27.07.2014 00:26, schrieb Rick Thomas:
> > On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
> >> So a future update of systemd will slightly change this behaviour:
> >> whenever there is a service that failed or takes longer then a certain
> >> thre
Am 27.07.2014 00:26, schrieb Rick Thomas:
>
> On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
>
>> So a future update of systemd will slightly change this behaviour:
>> whenever there is a service that failed or takes longer then a certain
>> threshold (iirc it's something like 5 secs), syste
On Jul 25, 2014, at 12:33 PM, Michael Biebl wrote:
> So a future update of systemd will slightly change this behaviour:
> whenever there is a service that failed or takes longer then a certain
> threshold (iirc it's something like 5 secs), systemd will automatically
> switch into verbose mode
W
On 2014-07-26, Michael Biebl wrote:
>
> You can use the journal for that. It captures everything.
> Try journalctl -alb
>
I tried as both a regular user and as root to no avail. I searched for
it with apt-cache with equally disappointing results (I am still using
squeeze).
I now understand tha
Am 26.07.2014 12:03, schrieb Mark Carroll:
> Curt writes:
>
>> On 2014-07-25, Brian wrote:
>>>
>>> With sysvinit the default at booting is for the screen messages to fly
>>> past at a bewildering speed and then for the screen to be cleared by
>>> agetty. Nobody particularily complains about this
Curt writes:
> On 2014-07-25, Brian wrote:
>>
>> With sysvinit the default at booting is for the screen messages to fly
>> past at a bewildering speed and then for the screen to be cleared by
>> agetty. Nobody particularily complains about this behaviour. Unless
>> you have an excellent visual m
Hi Michael,
On Fri, 2014-07-25 at 21:33 +0200, Michael Biebl wrote:
> Hi,
>
> Am 25.07.2014 20:27, schrieb Steven Post:
>
> > I'm running Jessie (lagging about 5 days behind with the updates) and
> > use systemd-sysv. Today I noticed that there is no visual feedback from
> > fsck when checking a
On 2014-07-25, Brian wrote:
>
> With sysvinit the default at booting is for the screen messages to fly
> past at a bewildering speed and then for the screen to be cleared by
> agetty. Nobody particularily complains about this behaviour. Unless
> you have an excellent visual memory you are in the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
(Sorry if this turns out to be a resend; there's been a hiccup on my
end, and due to the usual variable lag before I receive messages I send
to the Debian lists, I don't know if it got sent before or not.)
On 07/25/2014 04:21 PM, Michael Biebl wrote
On Fri 25 Jul 2014 at 16:02:18 -0400, The Wanderer wrote:
> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>
> > Hi,
> >
> > Am 25.07.2014 20:27, schrieb Steven Post:
> >
> >> I'm running Jessie (lagging about 5 days behind with the updates)
> >> and use systemd-sysv. Today I noticed that there i
Am 25.07.2014 22:21, schrieb Michael Biebl:
> Am 25.07.2014 22:02, schrieb The Wanderer:
>> Is there any plan to do either of these things in the Debian-default
>> configuration (and possibly update existing installs to match, if
>> unmodified)?
>
> No, there is no such plan.
What I do plan to d
Am 25.07.2014 22:02, schrieb The Wanderer:
> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>
>> Hi,
>
>> Am 25.07.2014 20:27, schrieb Steven Post:
>
>>> I'm running Jessie (lagging about 5 days behind with the updates)
>>> and use systemd-sysv. Today I noticed that there is no visual
>>> feedback
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/25/2014 03:33 PM, Michael Biebl wrote:
> Hi,
>
> Am 25.07.2014 20:27, schrieb Steven Post:
>
>> I'm running Jessie (lagging about 5 days behind with the updates)
>> and use systemd-sysv. Today I noticed that there is no visual
>> feedback fr
Hi,
Am 25.07.2014 20:27, schrieb Steven Post:
> I'm running Jessie (lagging about 5 days behind with the updates) and
> use systemd-sysv. Today I noticed that there is no visual feedback from
> fsck when checking an ext4 filesystem at boot time. Since it appears the
> system is stuck (apart from
Hello list,
I'm running Jessie (lagging about 5 days behind with the updates) and
use systemd-sysv. Today I noticed that there is no visual feedback from
fsck when checking an ext4 filesystem at boot time. Since it appears the
system is stuck (apart from the HDD LED) I would consdider this a bug.
Matej Kosik:
>
> I am trying to figure out the meaning of:
>
> /proc/$PID/fd/*
>
> files.
These files represent the open files of a process. On recent systems you
can even see the associated "real" files, if any:
# ls -l /proc/6373/fd
total 0
lr-x-- 1
> I am trying to figure out the meaning of:
>
> /proc/$PID/fd/*
>
> files.
These are links that point to the open files of the process whose pid is
$PID. Fd stands for "file descriptors", which is an integer that
identifies any program input or output in UNIX-like
Hello,
I am trying to figure out the meaning of:
/proc/$PID/fd/*
files.
As:
- their name suggests
- as most of the descriptions on the web around indicate
- and consistently with wishful thinking
I thought that writing to /proc/$PID/0 would mean that designated
process will receive
On Sun, 10 Jun 2012 23:05:10 +1200 "Chris Bannister
cbannis...@slingshot.co.nz" suggested this:
>"apt-get update" THEN "apt-cache policy firmware-linux-nonfree"
I didn't copy the output because it was the same again. That being that:
firmware-linux-nonfree wasn't in the package list.
So, becau
On Sun, Jun 10, 2012 at 03:08:09PM +1000, Charlie wrote:
> On Sun, 10 Jun 2012 14:14:15 +1200 "Chris Bannister
> >Looks like a problem with your mirror. Just to be sure, can you do:
> >apt-get update && apt-cache policy firmware-linux-nonfree
> Here tis:
>
> apt-cache policy && firmware-linux-n
On Sun, 10 Jun 2012 14:14:15 +1200 "Chris Bannister
cbannis...@slingshot.co.nz" suggested this:
>On Sat, Jun 09, 2012 at 09:31:47PM +1000, Charlie wrote:
>> >> On Sat, 9 Jun 2012 18:28:52 +1200 "Chris Bannister
>> >What is output of:
>> >"apt-cache policy firmware-linux-nonfree"?
>>
>> Booted
On Sat, Jun 09, 2012 at 09:31:47PM +1000, Charlie wrote:
> >> On Sat, 9 Jun 2012 18:28:52 +1200 "Chris Bannister
> >What is output of:
> >"apt-cache policy firmware-linux-nonfree"?
>
> Booted the lappy and my /etc/apt/sources.list contains:
>
> deb http://ftp.au.debian.org/debian/ testing main n
On Sat, 9 Jun 2012 22:00:31 +1200 "Chris Bannister
cbannis...@slingshot.co.nz" suggested this:
>On Sat, Jun 09, 2012 at 05:54:53PM +1000, Charlie wrote:
>> On Sat, 9 Jun 2012 18:28:52 +1200 "Chris Bannister
>> cbannis...@slingshot.co.nz" suggested this:
>>
>> >It's a wheezy [testing] system a
On Sat, Jun 09, 2012 at 05:54:53PM +1000, Charlie wrote:
> On Sat, 9 Jun 2012 18:28:52 +1200 "Chris Bannister
> cbannis...@slingshot.co.nz" suggested this:
>
> >It's a wheezy [testing] system and aptitude search firmware doesn't off
> >> me that package?
> >
> >Is the non-free entry in "/etc/a
On Sat, 9 Jun 2012 18:28:52 +1200 "Chris Bannister
cbannis...@slingshot.co.nz" suggested this:
>It's a wheezy [testing] system and aptitude search firmware doesn't off
>> me that package?
>
>Is the non-free entry in "/etc/apt/sources.list" ?
I do
>
>i.e:
>tal% less /etc/apt/sources.list
>deb
On Thu, Jun 07, 2012 at 08:03:11AM +1000, Charlie wrote:
> On Wed, 6 Jun 2012 19:45:13 +0100 "Keith McKenzie km3...@gmail.com"
> suggested this:
>
> >If you haven't tried 'firmware-non-free', it may be in there, mine was.
>
> It's a wheezy [testing] system and aptitude search firmware doesn't o
On Wed, 6 Jun 2012 19:45:13 +0100 "Keith McKenzie km3...@gmail.com"
suggested this:
>If you haven't tried 'firmware-non-free', it may be in there, mine was.
It's a wheezy [testing] system and aptitude search firmware doesn't off
me that package?
Be well,
Charlie
--
** ** ** ** ** ** **
[QUOTE]I have installed all the firmware and other packages that might work I
think. If you have an idea about what I might have left out please
don't hesitate to say.
Thank you,
Charlie
--[/QUOTE]
If you haven't tried 'firmware-non-free', it may be in there, mine was.
--
Sent from FOSS (Free O
On Wed, 06 Jun 2012 08:59:53 +1000, Charlie wrote:
> On Tue, 5 Jun 2012 15:41:57 + (UTC) "Camaleón noela...@gmail.com"
> suggested this:
>>1/ Despite the warning on the PID, is the wireless connection still
>>available and working?
>
> Yes, it appears
On Wed, 6 Jun 2012 09:10:30 +0100 "Keith McKenzie km3...@gmail.com"
suggested this:
>[QUOTE]Toshiba laptop with an Intel wireless adapter that I'm unable
>to get to work[/QUOTE]
>
>Is it dead or, maybe, it just needs some firmware to be installed.
I have installed all the firmware and other pac
gested this:
>
>>Okay, let's back to the warning message and the behaviour you get.
>>Some questions:
>>
>>1/ Despite the warning on the PID, is the wireless connection still
>>available and working?
>
> Yes, it appears to pick it up on the second try as show
On Tue, 5 Jun 2012 15:41:57 + (UTC) "Camaleón noela...@gmail.com"
suggested this:
>Okay, let's back to the warning message and the behaviour you get.
>Some questions:
>
>1/ Despite the warning on the PID, is the wireless connection still
>available and workin
>>>
>>> bound to xxx.xxx.x.xxx -- renewal in 34212 seconds. cat:
>>> /var/run/wpa_supplicant.wlan1.pid: No such file or directory
>>
>>(...)
>>
>>Are you running Squeeze? If yes, it could be this bug:
>>
>>http://bugs.debian.org/cgi-bin/b
On Mon, 4 Jun 2012 15:25:18 + (UTC) "Camaleón noela...@gmail.com"
suggested this:
>> I get this message:
>>
>> Sometimes the connection fails and sometimes it continues on as here:
>>
>> bound to xxx.xxx.x.xxx -- renewal in 34212 seconds.
>&
On Mon, 04 Jun 2012 10:46:19 +1000, ariestao wrote:
> I get this message:
>
> Sometimes the connection fails and sometimes it continues on as here:
>
> bound to xxx.xxx.x.xxx -- renewal in 34212 seconds.
> cat: /var/run/wpa_supplicant.wlan1.pid: No such file or director
I get this message:
Sometimes the connection fails and sometimes it continues on as here:
bound to xxx.xxx.x.xxx -- renewal in 34212 seconds.
cat: /var/run/wpa_supplicant.wlan1.pid: No such file or directory
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems
Bob,
Thanks for your great explanation!
Malte
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/iif39c$5ic$1...@dough.gmane.org
be another
shell process between 'mycommand' and the 'su'.
> Because I might have to later send a signal to the mycommand process
> later, I then try to determine ist PID:
> CMDPID=$(ps -f --ppid $SUPID -C mycommand | awk 'NR == 2 { print $2 }')
> To my surprise,
e to later send a signal to the mycommand process
later, I then try to determine ist PID:
CMDPID=$(ps -f --ppid $SUPID -C mycommand | awk 'NR == 2 { print $2 }')
To my surprise, CMDPID often was empty. I wrapped the above line into a
loop and found that it might take 2 or 3 attempts unti
Several people offered advise. The trick is really how to locate and
kill the parent process, because I have tried otherwise and failed.
Following suggestion from Bob Proulx, killing all processes would ends
up with corrupted temporary files in my case. Bob wrote in detail
explanation of how thinks
Richard Hector wrote:
> $$ is the pid of the current shell.
>
> $! is the pid of the most recent background process, so you could do:
>
> amuled & echo $! > amuled.pid
> ...
> kill `cat amuled.pid`
Since presumabely amuled forks itself into the background then putti
13612 zhangwei 1352 Sgrep mule
> > zhangwe...@mesopotamia:~$ kill 13595
> >
> > Note that I should always kill the least-numbered process, I tried
> > otherwise and always end up in trouble.
> >
> > Question is, how do I script-lize this? The only dif
ered process, I tried
> otherwise and always end up in trouble.
>
> Question is, how do I script-lize this? The only difficulty is to get
> the pid in script. I could use an one-liner awk script to analyses the
> output of ps, but that sounds overkill. Is there a bette
Zhang Weiwu writes:
> Question is, how do I script-lize this? The only difficulty is to get
> the pid in script. I could use an one-liner awk script to analyses the
> output of ps, but that sounds overkill. Is there a better way?
man killall
man pidof
--
John Hasler
--
To UNSUBSCRI
to get
the pid in script. I could use an one-liner awk script to analyses the
output of ps, but that sounds overkill. Is there a better way?
Best. & Thanks in advance!
Hi ,
As already mentioned by Bob Proulx pkill & pgrep are better than ps for
such kind of tasks .
Reagrds ,
Alex
Zhang Weiwu wrote:
> zhangwe...@mesopotamia:~$ ps ax | grep mule
> 13595 zhangwei 14080 R N amuled
> 13598 zhangwei 14080 S N amuled
> 13600 zhangwei 14080 S N amuled
> 13603 zhangwei 14080 S N amuled
> 13612 zhangwei 1352 Sgrep mule
> zhangwe...@mesopotamia:~$ kill 13595
> Note that I s
rsonal preference):
ps -efH
BSD-like
ps axf
But do you need to see all processes? Won't you be the owner of that
process?
ps xf
> Question is, how do I script-lize this? The only difficulty is to get
> the pid in script. I could use an one-liner awk script to analyses the
>
13603 zhangwei 14080 S N amuled
13612 zhangwei 1352 Sgrep mule
zhangwe...@mesopotamia:~$ kill 13595
Note that I should always kill the least-numbered process, I tried
otherwise and always end up in trouble.
Question is, how do I script-lize this? The only difficulty is to get
the pid in
["Followup-To:" header set to gmane.linux.ubuntu.user.]
On Wed, 26 Oct 2005 09:54:51 +0200, Tshepang Lekhonkhobe
<[EMAIL PROTECTED]> wrote:
> Hello,
> I'm having problems with the later (post-Sarge) procps package and
> specifically the top binary. If I select to
Hello,
I'm having problems with the later (post-Sarge) procps package and
specifically the top binary. If I select to sort the output by PID
(the leftmost column) the output becomes scrambled. I experienced this
problem also with the the same package from Hoary but not in the older
ones (Sarg
Sometime in August Richard A Nelson assaulted the keyboard and produced:
| upgrade apache2 *and* any modules (ie apache2-mod-security)
| to the latest levels and this should no longer be an issue
Ok, I'll do this.
A question from someone rather new to Debian. Is there an email list
(similar to
1 - 100 of 167 matches
Mail list logo
