On 04/30/2011 01:49 AM, Pablo Neira Ayuso wrote:

> Could you develop the scenario a bit? The problem that you refer would
> occur if `-d' and `-e' are used?
> 

Hi,

the attached config file is the result of 'write' in the VTY code, e.g. it
contains the current stderr config.

$ ./src/osmo-bsc/osmo-bsc -c openbsc.bsc -e 1

now the -e 1 is applied (log_set_log_level(stderr_target, atoi(optarg));)
before the call to bsc_bootstrap_network. So somehow we should define what
takes precedence and make this work across our utilities. E.g. osmo-bsc and
osmi-nitb behave the same right now (-e 1 being ignored if stderr is
configured in the config file).

With osmo-bsc one sees a lot more messages on startup if -e 1 is applied.

holger



!
! OsmoBSC (0.9.13.88-0b03) configuration saved from vty
!!
password foo
!
log stderr
  logging color 1
  logging timestamp 0
  logging level all everything
  logging level rll notice
  logging level cc notice
  logging level mm notice
  logging level rr notice
  logging level rsl notice
  logging level nm info
  logging level mncc notice
  logging level sms notice
  logging level pag notice
  logging level meas notice
  logging level mi notice
  logging level mib notice
  logging level mux notice
  logging level inp notice
  logging level sccp notice
  logging level msc notice
  logging level mgcp notice
  logging level ho notice
  logging level db notice
  logging level ref notice
  logging level gprs debug
  logging level ns info
  logging level bssgp debug
  logging level llc debug
  logging level sndcp debug
  logging level nat notice
!
line vty
 no login
!
network
 network country code 204
 mobile network code 9
 short name OpenBSC
 long name OpenBSC
 auth policy closed
 location updating reject cause 13
 encryption a5 0
 neci 1
 paging any use tch 0
 rrlp mode none
 mm info 0
 handover 0
 handover window rxlev averaging 10
 handover window rxqual averaging 1
 handover window rxlev neighbor averaging 10
 handover power budget interval 6
 handover power budget hysteresis 3
 handover maximum distance 9999
 timer t3101 10
 timer t3103 0
 timer t3105 0
 timer t3107 0
 timer t3109 0
 timer t3111 0
 timer t3113 60
 timer t3115 0
 timer t3117 0
 timer t3119 0
 timer t3122 0
 timer t3141 0
 dtx-used 0
 subscriber-keep-in-ram 0
 bts 0
  type nanobts
  band DCS1800
  cell_identity 30000
  location_area_code 666
  training_sequence_code 7
  base_station_id_code 63
  ms max power 15
  cell reselection hysteresis 4
  rxlev access min 0
  channel allocator ascending
  rach tx integer 9
  rach max transmission 7
  rach nm busy threshold 255
  rach nm load average 200
  ip.access unit_id 23 0
  oml ip.access stream_id 255
  paging free 5
  neighbor-list mode automatic
  trx 0
   rf_locked 0
   arfcn 874
   nominal power 23
   max_power_red 10
   rsl e1 tei 0
    timeslot 0
     phys_chan_config CCCH+SDCCH4
     hopping enabled 0
    timeslot 1
     phys_chan_config SDCCH8
     hopping enabled 0
    timeslot 2
     phys_chan_config TCH/F
     hopping enabled 0
    timeslot 3
     phys_chan_config TCH/F
     hopping enabled 0
    timeslot 4
     phys_chan_config TCH/F
     hopping enabled 0
    timeslot 5
     phys_chan_config TCH/F
     hopping enabled 0
    timeslot 6
     phys_chan_config TCH/F
     hopping enabled 0
    timeslot 7
     phys_chan_config TCH/F
     hopping enabled 0
e1_input
msc
 token BLA
 core-mobile-network-code 45
 core-mobile-country-code 104
 ip.access rtp-base 4000
 timeout-ping 30
 timeout-pong 20
 mid-call-timeout 0
 bsc-rf-socket /tmp/foo4
 codec-list hr3
 dest 127.0.0.1 5000 32

Reply via email to