search for: daytim

Hi all, One of the centos 5.1 servers was scanned by a customer and he suggests turning off daytime on port 13. When I look at /etc/xinetd.d/daytime* the 2 files say disabled yes So is there something else I should be looking at ? Thanks, Jerry

Is it possible to build a dialplan in which shifting from daytime to nightime is not hour based but phone driven ???

...data being backed up is about 2GB from the 6GB disk. The Sun system is an Ultra 10 running Solaris 8, and I'm using openSSH 2.1.1p1 on the Sun; 2.1.1p2 on the PC. Backup occurs over our local network, which may have its problems but is generally okay. When I was testing the setup - during the daytime - the backup took about one hour. This was with me doing other things on the PC whilst it was going on. Again, no problem. I configured the backup to run overnight via cron on the PC. It was to start at 1am. However, it took over 8 hours for the backup to complete! The throughput from the log fil...

good day i read about relativity gem but when i try to use it and make a test file and build it gives me an error =test.rb= <pre> require ''relativity'' opens_at = DayTime.new(9) #=> 09:00:00 closes_at = DayTime.new(12,30) #=> 12:30:00 </pre> <pre> /home/start/.rvm/gems/ruby-1.9.2-p290/gems/relativity-0.0.8/lib/ relativity/day_time/new.rb:24:in `BigDecimal'': can''t convert Fixnum into String (TypeError) from /home/start/.rvm/gem...

When setting include => daytime|9:00-21:00|mo-fri|*|* How does this determine what is different between 9 AM and 9 PM And after hours ??? I want different hours on Saturday and Sunday And a different welcome message after hours Any help appreciated Regards Mick

Hi Bob, >> A big compile time regression. Any ideas? >> >> Ciao, Duncan. > > False alarm. For some reason that I have not yet been able to figure out, these tests run significantly more slowly when I run them during the daytime, which I did for that run. I checked a few of the worst regressions reported here and they all recovered in subsequent runs. here is a crazy idea: during the day the room the computer is in is hotter, and to avoid overheating the CPU frequency is reduced, resulting in the machine running slower....

Hi, I have a data.frame that contains a variable act which records the duration (in seconds) of two states (wet-dry) for several individuals (identified by Ring) over a period of time. Since I want to work with daytime (i.e. from sunrise till sunset) and night time (i.e. from sunset till next sunrise), I have to split act from time[i] till sunset and from sunset until time[i+1], and from time[k] till sunrise and from sunrise until time[k+1]. Here is an example with time and act separated by a comma: [i] 01-01-...

...0", hosts "dmz" and "dmz" are connected through bridge "xenbr1". Routing tables are at the end of this post. Note that there''s no firewall installed (yet); it''s just plain routing at the moment. All hosts have inetd running, with services "daytime" and "echo" active; these services are great diagnostics; they''re simple and when "echo" works then more complicated things like ssh will too. What works? * ping from everywhere to everywhere (traceroute too) * full access from everywhere to "fw" * f...

...;fw" are connected to bridge "xenbr0", hosts "dmz" and "dmz" are connected through bridge "xenbr1". Note that there''s no firewall installed (yet); it''s just plain routing at the moment. All hosts have inetd running, with services "daytime" and "echo" active; these services are great diagnostics; they''re simple and when "echo" works then more complicated things like ssh will too. What works? * ping from everywhere to everywhere (traceroute too) * full access from everywhere to "fw" * f...

My data frame shows changes on the variable act which records the consecutive duration (in seconds) of two states (wet-dry) over a few days for several?individuals (identified by Ring). Since I want to work with daytime (i.e. from dawn till dusk) and night time (i.e. from dusk till next dawn), I have to split act in two: from time[i] till dusk and from dusk until time[i+1], and from time[k] till dawn and from dawn until time[k+1]. Example: ith row: 01-01-2000 20:55:00 act= 360 seconds i+1th row: 01-01-2000 21:0...

When I am trying to run an application under wine, I am getting this error in console. Code: fixme:ntdll:find_reg_tz_info Can't find matching timezone information in the registry for bias 180, std (d/m/y): 17/02/2008, dlt (d/m/y): 19/10/2008 What is this and what I can do to solve it? The application is an license manager (lmgrd). I am using Ubuntu 8.10 x64 and wine is 1.1.8 []'s

So I have my extensions.conf (http://www.infiltrated.net/exten.stupidity.conf) shortened in case someone wants to look. Has someone encountered the following? I've racked my brain on this for too long... I have two contexts, day and night... Caller (Daytime) --> Dials an extension --> Caller hears extension ring on receiver --> Call goes through Caller (Night) --> Dials an extension --> Caller hears silence until vm picks up --> Leaves a voicemail... Significant albeit insanely stupid Asstricks message: 2007-01-30 09:22:57 DEBUG...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

Dear R-Users, I have a data file with timestamps and I wanted to use POSIXct time data type to represent the respective column. I played around with the type and found a couple of issues: * there seems to be no direct way of reading datetimes into a variable. Let's say this is my file "1992-02-27 23:03:20 PST" "1992-02-27 22:29:56 PST" "1992-01-14 01:03:30 PST"

Hi,   I have a dataset which contains several time records for a number of days, plus a variable (light) that allows to determine night time (lihgt= 0) and daytime (light> 0). I need to obtain get dusk time and dawn time for each day and place them in two columns. This is the starting point (d): day time light 1     1       20 1     12     10 1     11     6 1     9       0 1     6       0 1     12     0 ... 30     8     0 30     3     0 30     8...

...ude => operator include => e911 include => forced-analog include => fwd-out include => information include => local include => toll-free include => long-distance ; sip lines [nighttime-fwd1] exten => s,1,Wait(2) exten => s,2,Background(nighttime) exten => 1,1,Goto(daytime-sip1,s,1) exten => 2,1,Voicemail(u2201) exten => 3,1,Voicemail(u2206) exten => 4,1,Voicemail(u2202) exten => 9,1,Playback(transfer) exten => 9,2,Goto(local,2206,1) [daytime-fwd1] exten => s,1,Dial(${MAINPHONE}&${KITCHEN},15) exten => s,2,Dial(${JESSICA},6) exten => s,3...

...AllowAuth neverneverland:/# nmap localhost Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-05-17 23:49 CDT Interesting ports on neverneverland (127.0.0.1): (The 1656 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 9/tcp open discard 13/tcp open daytime 22/tcp open ssh 25/tcp open smtp 37/tcp open time 113/tcp open auth 6666/tcp open irc-serv Nmap finished: 1 IP address (1 host up) scanned in 0.726 seconds What do I need to do to close these ports?

...T STATE SERVICE 1/tcp open tcpmux 2/tcp open compressnet 3/tcp open compressnet 4/tcp open unknown 5/tcp open rje 6/tcp open unknown 7/tcp open echo 8/tcp open unknown 9/tcp open discard 11/tcp open systat 12/tcp open unknown 13/tcp open daytime 14/tcp open unknown 15/tcp open netstat 16/tcp open unknown 17/tcp open qotd 20/tcp open ftp-data 22/tcp open ssh 24/tcp open priv-mail 25/tcp open smtp 26/tcp open unknown

...owing wiki item for more information: http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages The repository for Dovecot v1.2 has been defunct for a few months now and is expected to be removed soon. For the coming month or so, the builders at Xi will not be active during Dutch daytime. There are some issues with the virtual host's I/O performance that need to be resolved first. Regards, Stephan.

...text 'default' [1;30;40m -- [0;37;40mAdded extension '_9X.' priority 1 to default [1;30;40m -- [0;37;40mAdded extension '_908X.' priority 1 to default [1;30;40m -- [0;37;40mRegistered extension context 'office' [1;30;40m -- [0;37;40mIncluding context 'daytime' in context 'office' [1;30;40m -- [0;37;40mIncluding context 'prepaid' in context 'office' [1;30;40m -- [0;37;40mIncluding context 'staff' in context 'office' [1;30;40m -- [0;37;40mRegistered extension context 'prepaid' [1;30;40m -- [...