search for: l263

...it trying to "kill"? > When you say the "first" upsmon case, do you mean this line? > > https://github.com/networkupstools/nut/blob/master/clients/upsmon.c#L1923 The kill error is coming from this line: https://github.com/networkupstools/nut/blob/master/common/common.c#L263 Which is called from: https://github.com/networkupstools/nut/blob/master/client/upsmon.c#L1930 In which case would you need to "see if this is going to work first"? > >> If this is normal operation, maybe they shouldn't be printed to the console? > > Agreed. It would...

...ec(s) g729 Outbound H.323 call 'ip$localhost/263'. -- Called 2348033045670@209.3.12.49 Call 'ip$localhost/263' cleared. -- H.323 call 'ip$localhost/263' cleared, reason 24 (Call ended with Q.931 cause) Call 'ip$localhost/263' cleared in INIT state. -- OH323/L263 is busy -- Hungup 'OH323/L263' == Everyone is busy/congested at this time (1:1/0/0) -- Executing Hangup("Zap/3-1", "") in new stack == Spawn extension (incoming, s, 3) exited non-zero on 'Zap/3-1' -- Hungup 'Zap/3-1' Call 'ip$localhost/263...

On Aug 1, 2013, at 1:34 AM, Kris Jordan wrote: > The kill error is coming from this line: > https://github.com/networkupstools/nut/blob/master/common/common.c#L263 > > Which is called from: > https://github.com/networkupstools/nut/blob/master/client/upsmon.c#L1930 > > In which case would you need to "see if this is going to work first"? Agreed, the first kill(pid, 0) is redundant in that case. https://github.com/networkupstools/nu...

...er-like manner. class Model include ActiveModel::Dirty def self.property(name, klass = String) define_property_accessors(name, klass) # This method will be called once, because of https://github.com/rails/rails/blob/master/activemodel/lib/active_model/attribute_methods.rb#L263 define_attribute_methods([name]) end end class Article < Model property :title property :body property :published_at, Time end In the above example, attribute methods will be defined just for :title. I don''t see any nice workaround. So what is the purpose of A...

...blem by just not creating > > /etc/init.d > > > > My problem right now is to have supermin recognized xz modules. I've > been > > working on that. > > This is the bit you need to modify: > > https://github.com/libguestfs/supermin/blob/master/helper/init.c#L263 > > You can post patches on the libguestfs at redhat.com mailing list. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > libguestfs lets you edit virtual machines. Supports shell scripting, > bindings from many langua...

On Jul 30, 2013, at 1:36 PM, Kris Jordan wrote: > upsd removes its pid files when it's stopped, upsmon does not. Hmm, interesting observation. Offhand, I think both should remove the PID files, but the way that upsmon drops root privileges might make this difficult. > If I remove upsmon's manually after stopping it, I get a different message for it when I start it back up... >

Centos5 NUT 2.6.5, compiled from source I was reminded by a previous thread about a message I get when starting NUT... Starting upsd: fopen /var/run/nut/upsd.pid: No such file or directory Starting upsmon: kill: No such process upsd removes its pid files when it's stopped, upsmon does not. If I remove upsmon's manually after stopping it, I get a different message for it when I start