Re: strange behaviour sys.argv

2007-04-16 Thread Charles Sanders
schnupfy wrote: > > ok, thanks for the answers. I try to hand over the 3rd part (the long > trap) as one cmd argument. I will ask in a shell ng. Thanks again. > > Cheers Should be as simple as removing the backslashes /root/mk/services.py $HOST $SEVERITY "$TRAP" should pass TRAP as a s

Re: strange behaviour sys.argv

2007-04-16 Thread schnupfy
On Apr 17, 3:00 pm, Charles Sanders <[EMAIL PROTECTED]> wrote: > Michael Hoffman wrote: > > schnupfy wrote: > > >> I am not used to python and I am wondering about this thing: > > > This is not a Python question. It is a question about how to use bash. > > [snip] > > Michael is correct, it is a bas

Re: strange behaviour sys.argv

2007-04-16 Thread Charles Sanders
Michael Hoffman wrote: > schnupfy wrote: > >> I am not used to python and I am wondering about this thing: > > This is not a Python question. It is a question about how to use bash. > [snip] Michael is correct, it is a bash thing, nothing to do with python. bash (and other *nix like shells) gen

Re: strange behaviour sys.argv

2007-04-16 Thread Michael Hoffman
schnupfy wrote: > I am not used to python and I am wondering about this thing: This is not a Python question. It is a question about how to use bash. I would try to help anyway, but I am unsure what results you actually want. Your example is too complicated as well. You should strip down your

strange behaviour sys.argv

2007-04-16 Thread schnupfy
Hi, I am not used to python and I am wondering about this thing: If I execute this from the shell: /root/mk/services.py 192.168.1.101 critical "192.168.1.101 192.168.1.101 SNMPv2-MIB::sysUpTime.0 14:13:02:57.06 SNMPv2- MIB::snmpTrapOID.0 SNMPv2-SMI::enterprises.789.0.13 SNMPv2- SMI::enterprises.