Здравствуйте.

   Пробую задействовать NeTAMS (netams-3.1.1829-alt1) для управления 
squid (через access-script). Но при вызове скрипта - демон падает 
(если параметр access-script закоминтировать - всё работает).

   В процессе отладки обнаружил, что скрипту передаются повидимому 
"грязные" параметры (содержат странные символы).

   Скрипт (action.sh он довольно сырой) лог работы его работы 
(action.log) прилагаю.

   Выдержка netams.log, участок старт-падение (при включенной отладке):

++++++

NeTAMS version 3.1(1829.1) builder@mash / Mon Jul  5 13:41:15 MSD 2004
23.07.2004 20:10:33.2049 main [INFO]: Becoming a daemon...
23.07.2004 20:10:33.2153 scheduler [INFO]: service scheduler:0 
thread started
23.07.2004 20:10:33.2154 main [INFO]: service scheduler starting 
thread...
23.07.2004 20:10:33.2157 main [INFO]: scheduled to: 23.07.2004 20:59:50
23.07.2004 20:10:33.2157 scheduler [INFO]: service scheduler:0 
processing queue
23.07.2004 20:10:33.2158 main [INFO]: service server starting thread...
23.07.2004 20:10:33.2158 main [INFO]: service server:0 initialized
23.07.2004 20:10:33.2158 main [INFO]: server login permitted from 
localhost only
23.07.2004 20:10:33.2159 main [INFO]: server listen port set to 20001
23.07.2004 20:10:33.2159 main [INFO]: server maximum connections 
number is set to 2
23.07.2004 20:10:33.2159 server [INFO]: service server thread started
23.07.2004 20:10:33.2159 <..> [INFO]: service storage:1 thread 
started (0x8096290)
23.07.2004 20:10:33.2160 main [INFO]: service storage starting thread...
23.07.2004 20:10:33.2160 main [INFO]: service storage:1 initialized
23.07.2004 20:10:33.2161 <..> [INFO]: service data-source:0 thread 
started (0x8096500)
23.07.2004 20:10:33.2161 main [INFO]: service data-source starting 
thread...
23.07.2004 20:10:33.2161 main [INFO]: service data-source:0 initialized
23.07.2004 20:10:33.2162 main [INFO]: service data-source starting 
thread...
23.07.2004 20:10:33.2162 main [INFO]: service data-source:1 initialized
23.07.2004 20:10:33.2163 main [INFO]: service monitor starting thread...
23.07.2004 20:10:33.2163 main [INFO]: service monitor:1 initialized
23.07.2004 20:10:33.2164 data-source [INFO]: service data-source:1 
thread started (0x80966c0)
23.07.2004 20:10:33.2164 <..> [INFO]: service processor thread started
23.07.2004 20:10:33.2164 main [INFO]: service processor starting 
thread...
23.07.2004 20:10:33.2164 main [INFO]: service processor:0 initialized
23.07.2004 20:10:33.2340 <..> [INFO]: service html:0 thread started 
(0x80e2018)
23.07.2004 20:10:33.2341 main [INFO]: service html starting thread...
23.07.2004 20:10:33.2341 main [INFO]: service html:0 initialized
23.07.2004 20:10:33.2342 main [INFO]: service html starting thread...
23.07.2004 20:10:33.2342 main [INFO]: service html:1 initialized
23.07.2004 20:10:33.2343 html [INFO]: service html:1 thread started 
(0x80e20c0)
23.07.2004 20:10:33.2343 <..> [INFO]: service alerter:0 thread 
started (0x80e2168)
23.07.2004 20:10:33.2343 main [INFO]: service alerter starting thread...
23.07.2004 20:10:33.2343 main [INFO]: service alerter:0 initialized
23.07.2004 20:10:33.2344 <..> [INFO]: service quota:0 thread started 
(0x80e22f0)
23.07.2004 20:10:33.2344 main [INFO]: service quota starting thread...
23.07.2004 20:10:33.2345 main [INFO]: service quota:0 initialized
23.07.2004 20:10:33.2346 main [INFO]: service login starting thread...
23.07.2004 20:10:33.2346 main [INFO]: service login:0 initialized
23.07.2004 20:10:33.2346 login [INFO]: service login:0 thread 
started (0x80e2598)
23.07.2004 20:10:34.2379 main [INFO]: wake up main:0 service: SKIPPED!
23.07.2004 20:10:34.2380 main [INFO]: waking up scheduler:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2380 main [INFO]: waking up server:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2380 main [INFO]: waking up storage:1 service: 
WAS_DOWN
23.07.2004 20:10:34.2381 main [INFO]: waking up data-source:0 
service: WAS_DOWN
23.07.2004 20:10:34.2381 main [INFO]: waking up data-source:1 
service: WAS_DOWN
23.07.2004 20:10:34.2381 main [INFO]: waking up monitor:1 service: 
WAS_UP
23.07.2004 20:10:34.2381 main [INFO]: waking up processor:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2381 main [INFO]: waking up html:0 service: WAS_DOWN
23.07.2004 20:10:34.2382 main [INFO]: waking up html:1 service: WAS_DOWN
23.07.2004 20:10:34.2382 main [INFO]: waking up alerter:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2382 main [INFO]: waking up quota:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2382 main [INFO]: waking up login:0 service: 
WAS_DOWN
23.07.2004 20:10:34.2382 main [INFO]: NeTAMS is now operational, 
23.07.2004 20:10:34
23.07.2004 20:10:34.2383 server [INFO]: server is listening
23.07.2004 20:10:34.2384 storage [INFO]: storage:1 working with SQL
23.07.2004 20:10:34.2385 data-source [WARN]: no rule for pcap, 
capturing all
23.07.2004 20:10:34.2386 data-source [INFO]: Libpcap: ethernet interface
23.07.2004 20:10:34.2386 data-source [INFO]: Hook is installed by ds:0
23.07.2004 20:10:34.2389 data-source [INFO]: Hook is installed by ds:1
23.07.2004 20:10:34.2391 processor [INFO]: using storage:1, 
in=0x80962c8, out=0x8096308, service_cfg=0x8096290
23.07.2004 20:10:34.2391 processor [INFO]: using storage:1 as source 
for READ and STAT requests
23.07.2004 20:10:34.2414 alerter [INFO]: service alerter:0 
processing queue
23.07.2004 20:10:34.2550 quota [INFO]: Restoring unit 02440B 
(host_192.168.52.201) violated quota
23.07.2004 20:10:34.2612 quota [INFO]: cAccessScriptCall oid 02440B 
action 1 system:512

------

-- 

С уважением. Алексей.