[SLVED] Re: how to get pid when I start the process

[Zhang Weiwu]

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 works which should serve great reference
material for new reader/learners on the list.

One idea offered by Chris Davies is to find the process with R tag, but
I tried and end up feeling that one isn't always the parent process.

Bill Dennen and Richard Hector together offered the advice to run the
process in foreground and sink them to background with shell '&'
postfix, and then obtaining the sunken process' ID from the shell using
special '$!', which works wonderfully for me, thus solved the case.

Thanks all for comments.


-- 
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/4d16c883.8030...@realss.com

Re: Problems with Pacemaker + Corosync after reboot

[Peter Beck]

On Sun, 2010-12-19 at 21:06 -0300, Daniel Bareiro wrote:
> # ps auxf
> [...]
> root  1508  0.1  1.9 182624  4880 ?Ssl  15:52
> 0:22 /usr/sbin/corosync
> root  1539  0.0  1.2 168144  3240 ?S15:52   0:00
> \_ /usr/sbin/corosync 

Hi Daniel

have you tried to kill corosync with "killall -9 corosync"
and then to restart via "/etc/init.d/corosync start" ?

This seems to bring back my nodes. If I do this, both nodes here are
back. But it does not solve the issue, every reboot I have to do it
again. Maybe corosync starts too early at bootup and one of the
depending services is not ready at this time ?

Best Regards
Peter



-- 
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/1293314479.2491.10.ca...@peanut.datentraeger.li

Re: 2 Ethernet cabling question

[briand]

On Sat, 25 Dec 2010 11:47:12 -0500
Mark Neidorff  wrote:

> 
> The order was determined to minimize cross-talk on the adjacent
> wires.  Your best bet is to stay with the standard.  So, yes, the
> order is important.

yep, I know from personal experience that 100 won't work if you don't
use the proper order :-(


-- 
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/20101225112002.49b73...@windy.deldotd.com

Re: 2 Ethernet cabling question

[David Christensen]

S Mathias wrote:

Q1) when cabling, is the color order important? like:


Yes.  Conductor colors and pin terminations are per the standard 
TIA/EIA-568-B.1-2000:


http://en.wikipedia.org/wiki/TIA/EIA-568-B


Most factory-made Ethernet patch cables I've seen use T568B on both 
ends.  That's how I make my cables.



Crossover cables use T568B on one end and T568A on the other.



Q2) again cabling.. i know what is the color order of straight and crossover 
cabling. BUT: what are the color orders, when i need to create physically two 
separated networks?


Use a separate cable for each network connection.


I buy Category 5e riser cable for use with Fast and/or Gigabit Ethernet.


You will want a crimp tool, connectors, and cable tester.  My local home 
improvement store (Home Depot) carries products made by Ideal:


http://www.idealindustries.com/prodDetail.do?prodId=30-696

http://www.idealindustries.com/prodDetail.do?prodId=85-396

http://www.idealindustries.com/prodDetail.do?prodId=62-200


The Ideal LinkMaster Tester remote unit includes a useful T568A and 
T568B wiring diagram printed on its face.



HTH,

David


--
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/4d16404f.2060...@holgerdanske.com

Re: 2 Ethernet cabling question

[Mark Neidorff]

On Saturday 25 December 2010 09:42 am, S Mathias wrote:
> Two questions that was not always clear for me [sorry for posting to this
> list :\]:
>
> ###
>###
>
> Q1) when cabling, is the color order important? like:
>
> straight cabling:
> A side: white-orange, orange, white-green, blue, white-blue, green,
> white-brown, brown B side: white-orange, orange, white-green, blue,
> white-blue, green, white-brown, brown
>
> could be eg.: like this??
> A side: white-orange, brown, white-blue, green, white-green, blue,
> white-brown, orange B side: white-orange, brown, white-blue, green,
> white-green, blue, white-brown, orange
>
> ###
>###

The order was determined to minimize cross-talk on the adjacent wires.  Your 
best bet is to stay with the standard.  So, yes, the order is important.

>
> Q2) again cabling.. i know what is the color order of straight and
> crossover cabling. BUT: what are the color orders, when i need to create
> physically two separated networks?
>
> 568B; straight; nic to switch:
> A side: white-orange, orange, white-green, blue, white-blue, green,
> white-brown, brown B side: white-orange, orange, white-green, blue,
> white-blue, green, white-brown, brown --
> 568A; crossover; nic to nic: [it's not so important about from ~2005]:
> switch the pairs: 1&2 with 3&6 on one side:
> A side: white-green, green, white-orange, blue, white-blue, orange,
> white-brown, brown B side: white-orange, orange, white-green, blue,
> white-blue, green, white-brown, brown --
> one cable, two straight networks:
> A side:
>   I.:
>   II.:
> B side:
>   I.:
>   II.:
> --
> one cable, two crossover networks:
> A side:
>   I.:
>   II.:
> B side:
>   I.:
>   II.:
> --
> one cable, one straight and one crossover network:
> A side [straight]:
>   I.:
>   II.:
> B side [crossover]:
>   I.:
>   II.:
> --
> one cable, one crossover and one straight network:
> A side [crossover]:
>   I.:
>   II.:
> B side [straight]:
>   I.:
>   II.:
>
Please explain what you are trying to accomplish and at what network speeds.  
Off the top of my head, 10baseT networks used 4 wires and 100baseT used all 8 
wires.  If you are trying for 100baseT speeds, you have to use all 8 wires.

Did you notice how difficult the kind of cabling you want is to find?  There 
is a reason for that.

Mark


-- 
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/201012251147.12334.m...@neidorff.com

Re: 2 Ethernet cabling question

[Boyd Stephen Smith Jr.]

On Saturday 25 December 2010 08:42:52 S Mathias wrote:
> Two questions that was not always clear for me [sorry for posting to this
> list :\]:
> 
> ###
> ###
> 
> Q1) when cabling, is the color order important? like:
> 
> straight cabling:
> A side: white-orange, orange, white-green, blue, white-blue, green,
> white-brown, brown B side: white-orange, orange, white-green, blue,
> white-blue, green, white-brown, brown
> 
> could be eg.: like this??
> A side: white-orange, brown, white-blue, green, white-green, blue,
> white-brown, orange B side: white-orange, brown, white-blue, green,
> white-green, blue, white-brown, orange

Depends.  Firstly, non-standard order might confuse the heck out of other 
techs.  More important, if you are just installing the tips and the majority 
of the cable is pre-made, they might be using a twisting/braiding order that 
minimizes noise where using the standard cable ordering.  Naively, there's no 
problem; and using a non-standard order should work, but using the standard 
order is well-advised.

If you are twisting/braiding your own cable, the best ordering is based how 
you twist/braid the wires.

> ###
> ###
> 
> Q2) again cabling.. i know what is the color order of straight and
> crossover cabling. BUT: what are the color orders, when i need to create
> physically two separated networks?

I don't recommend combining more than the 8 wires in a single cable when doing 
ethernet.  Just run multiple cables and bind them together.

Cross-talk between cables is less of an issue than cross-talk between wires in 
a single cable.  However, you are correct that would be minimized by running 
all the wires in a single cable, IF you use the correct braiding/twisting 
order through the length of the cable.  I know the generic algorithm for 
braiding N straight wires in a round cable involves primitive roots of the 
modular ring N, but I don't know how to practically apply that to braiding my 
own cable.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.

Re: Image in kcf-format

[Martin Woschek]

Got it from a friend:
open in gimp as raw, indexed, offset 768, size 640x400, color map the
same image again. then set the whitepoint in the color levels to 64.
done.

hth
Martin

On Sat, 25 Dec 2010 15:53:46 +0100
Martin  wrote:

> Hi folks,
> 
> ich have stumbled upon some images in kcf-format from the early 1980s.
> Do you know any way to view or convert them?
> 
> Thanks in advance
> Martin
> 
> 


-- 
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/20101225171229.1544c...@tenem

Image in kcf-format

[Martin]

Hi folks,

ich have stumbled upon some images in kcf-format from the early 1980s.
Do you know any way to view or convert them?

Thanks in advance
Martin


-- 
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/20101225155346.0fad3...@tenem

2 Ethernet cabling question

[S Mathias]

Two questions that was not always clear for me [sorry for posting to this list 
:\]:

##

Q1) when cabling, is the color order important? like:

straight cabling:
A side: white-orange, orange, white-green, blue, white-blue, green, 
white-brown, brown
B side: white-orange, orange, white-green, blue, white-blue, green, 
white-brown, brown

could be eg.: like this??
A side: white-orange, brown, white-blue, green, white-green, blue, white-brown, 
orange
B side: white-orange, brown, white-blue, green, white-green, blue, white-brown, 
orange

##

Q2) again cabling.. i know what is the color order of straight and crossover 
cabling. BUT: what are the color orders, when i need to create physically two 
separated networks?

568B; straight; nic to switch:
A side: white-orange, orange, white-green, blue, white-blue, green, 
white-brown, brown
B side: white-orange, orange, white-green, blue, white-blue, green, 
white-brown, brown
--
568A; crossover; nic to nic: [it's not so important about from ~2005]:
switch the pairs: 1&2 with 3&6 on one side:
A side: white-green, green, white-orange, blue, white-blue, orange, 
white-brown, brown
B side: white-orange, orange, white-green, blue, white-blue, green, 
white-brown, brown
--
one cable, two straight networks:
A side: 
I.: 
II.: 
B side: 
I.: 
II.: 
--
one cable, two crossover networks:
A side: 
I.: 
II.: 
B side: 
I.: 
II.: 
--
one cable, one straight and one crossover network:
A side [straight]: 
I.: 
II.: 
B side [crossover]: 
I.: 
II.: 
--
one cable, one crossover and one straight network:
A side [crossover]: 
I.: 
II.: 
B side [straight]: 
I.: 
II.: 

##

Thank you for any pointings, links, or specific answers.

Happy Christmas!


  


-- 
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/300521.28446...@web121410.mail.ne1.yahoo.com

Re: lavcopts: Unknown suboption vcompressc

[Sthu Deus]

Thank You for Your time and answer, François:

> Maybe you can try vcodec instead of vcompressc ... vcompressc is not
> documented on the mencoder man pages.

All right, I will try it. - But my problem comes not from a bad
parameters string of mencoder but from after upgrading - from lenny to
squeeze. - That's why I have asked.

Also, I do not pretend it to be the best optimized solution. so if have
one, please, share it w/ me.


--
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/4d15d45e.ce7c0e0a.30bd.9...@mx.google.com

Re: lenny squeeze etc etc

[Freeman]

On Wed, Dec 22, 2010 at 06:41:54PM -0500, Miles Fidelman wrote:
> Darac Marjal wrote:
> >On 22/12/10 16:47, John Hasler wrote:
> >>>Out of curiosity why don't Windows and Mac count?
> >>The companies spend billions hammering the code name/number for the next
> >>version into everyone's head before releasing it.  Despite never having
> >>used Windows even I know that Microsoft's current OS release is Windows
> >>7 and the the previous one was Vista.  I don't know what Apple calls
> >>their current version, though.
> >Apple are still on version 10. They same as it's been for the last 10 years.
> Wow.. it really has been that long.  OS X (10) was the shift to a
> Mach Kernel and BSD based platform.  Major releases (courtesy of
> WikiPedia):
> 
>* Mac OS X Public Beta
>   "Kodiak"
>* Mac OS X v10.0  "Cheetah"
>* Mac OS X v10.1  "Puma"
>* Mac OS X v10.2  "Jaguar"
>* Mac OS X v10.3  "Panther"
>* Mac OS X v10.4  "Tiger"
>* Mac OS X v10.5  "Leopard"
>* Mac OS X v10.6  "Snow
>  Leopard" - current
>* Mac OS X v10.7 
>  "Lion" - upcoming
> 

Doesn't seem the best nomenclature. There is already duplication.  A panther
is a puma, jaguar, or leopard, depending on location.  They'll be in the
calicoes and tabbies soon enough, after bobcat and lynx.

-- 
Regards,
Freeman

"Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the
answer." --Somebody


-- 
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/20101223025346.ga8...@europa.office