Displaying 3 results from an estimated 3 matches for "45980".
Did you mean:
4598
2003 Apr 02
12
segmentation fault
...0.0 0.6 0:00 asterisk
15987 root 8 0 6440 6436 2144 S 0.0 0.6 0:00 asterisk
Top in several hours:
15986 root 9 0 9192 9188 2148 S 0.0 0.9 0:00 asterisk
15987 root 9 0 9192 9188 2148 S 0.0 0.9 0:00 asterisk
Top after a day:
27441 root 9 0 45980 44M 2156 S 0.0 4.5 0:00 asterisk
27442 root 8 0 45980 44M 2156 S 0.0 4.5 0:16 asterisk
Actually, I saw it over 50.
There were some warning messages on the way. For example:
Apr 1 23:22:33 WARNING[10251]: File chan_zap.c, Line 5248 (zt_pri_error):
PRI:
Read on 86 failed...
2010 Jun 22
1
which model suits for these kind of data
...ot linear)
sales date shopnuber total 20%profit 10%profit
2009-10-03 1 41891 2863 39028
2009-10-04 1 49152 7588 41564
2009-10-05 1 45804 23543 22261
2009-10-06 1 48395 48371 24
2009-10-07 1 48906 20204 28702
2009-10-08 1 47003 19442 27561
2009-10-09 1 46296 21635 24661
2009-10-10 1 45980 34791 11189
2009-10-11 1 48423 1483 46940
2009-10-12 1 48800 18500 30300
2009-10-13 1 40694 22068 18626
2009-10-14 1 47356 42361 4995
2009-10-15 1 41501 15964 25537
2009-10-16 1 44762 42296 2466
2009-10-17 1 48607 12023 36584
2009-10-18 1 47513 28275 19238
2009-10-19 1 44527 7927 36600
2009-10-20 1...
2002 Mar 18
0
reproducible ext3 corruption with sync option, 2.4.17, images available
I have been using ext3 filesystem from 2.4.17 kernel in the default
"ordered" mode on an 64 MB SanDisk compactflash. The disk itself was used on
NationalGeode embedded board.
The following entry was used in fstab (I know, may be stupid, but should not
crash the filesystem?)
/dev/hda1 / ext2 defaults,sync 1 1
After the board is switched off, it does not boot