Sponsored Content
Full Discussion: bad trap & continuous reboot
Top Forums UNIX for Dummies Questions & Answers bad trap & continuous reboot Post 56712 by forbin24 on Friday 8th of October 2004 01:04:40 PM
Old 10-08-2004
Thanks for the suggestions. I'll give them a try. The memory passed diags. Patches were not loaded within the past year.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Building a better mouse trap, or How many lines of code does it take to trap a mouse?

Hello all, I'm hoping to get a little insight from some of the wily veterans amongst you. I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
Discussion started by: mph
4 Replies

2. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

3. Solaris

Panic BAD TRAP errors

One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly? Thanks Margaret Floyd Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies

4. Shell Programming and Scripting

Cntl+z Trap is not detecting ??? Help required to add a trap detection ???

Hi folks, I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:.... The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies

5. Solaris

BAD TRAP: type=30 rp=2a10001b840 addr=2a000012040 mmu_fsr=0

Hello Gurus, I got a system reboot due to "unix: BAD TRAP: type=30 rp=2a10001b840 addr=2a000012040 mmu_fsr=0" on SUNW,Netra-CP2300. I guess it is caused by HW fault but not very sure, and don't know which part should be relaced incase it is HW reason really. Sincerely appreciate for your... (7 Replies)
Discussion started by: fangfang
7 Replies

6. Solaris

X2200 in reboot loop & mounting ZFS drive on other boxes

So I was patching a Solaris 10 U08 X86 X2200 box in preparation for an Oracle upgrade. Rebooted the box because the patches failed and the box will not boot successfully. I need to back up the zones on the 2 drives before going further. I pulled the drives and attempted to mount them on my Ubuntu... (0 Replies)
Discussion started by: LittleLebowski
0 Replies

7. Homework & Coursework Questions

VM trap may work differently than a pure install trap.

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: That is the last reply I received from my instructor, and I'm looking for some alternatives. When using... (2 Replies)
Discussion started by: newuser45
2 Replies

8. Shell Programming and Scripting

File Move & Sort by Name - Kick out Bad File Names & More

I have a dilemma, we have users who are copying files to "directory 1." These images have file names which include the year it was taken. I need to put together a script to do the following: Examine the file naming convention, ensuring it's the proper format (e.g. test-1983_filename-123.tif)... (8 Replies)
Discussion started by: Nvizn
8 Replies

9. Solaris

Df reporting double size of du after fsck & reboot

Solaris 8 running on a Sparcstation 5 (Aurora) with 170MHz processor and 256MB ram This is AFTER doing fsck and reboot. 820030k vs 385252k All other files in /usr/asm not in /usr/asm/sys or /usr/asm/data amount to 43k. The /usr/asm/lost+found is 8k. somehow df and other applications... (3 Replies)
Discussion started by: lcoreyl
3 Replies
Time::Fake(3pm) 					User Contributed Perl Documentation					   Time::Fake(3pm)

NAME
Time::Fake - Simulate different times without changing your system clock SYNOPSIS
Pretend we are running 1 day in the future: use Time::Fake '+1d'; Pretend we are running 1 year in the past: use Time::Fake '-1y'; Pretend the script started at epoch time 1234567: use Time::Fake 1234567; See what an existing script would do if run 20 years in the future: % perl -MTime::Fake="+20y" test.pl Run a section of code in a time warp: use Time::Fake; # do some setup Time::Fake->offset("+1y"); run_tests(); # thinks it's a year ahead Time::Fake->reset; # back to the present DESCRIPTION
Use this module to achieve the effect of changing your system clock, but without actually changing your system clock. It overrides the Perl builtin subs "time", "localtime", and "gmtime", causing them to return a "faked" time of your choice. From the script's point of view, time still flows at the normal rate, but it is just offset as if it were executing in the past or present. You may find this module useful in writing test scripts for code that has time-sensitive logic. USAGE
Using and importing: use Time::Fake $t; Is equivalent to: use Time::Fake; Time::Fake->offset($t); See below for arguments to "offset". This usage makes it easy to fake the time for existing scripts, as in: % perl -MTime::Fake=+1y script.pl offset Time::Fake->offset( [$t] ); $t is either an epoch time, or a relative offset of the following form: +3 # 3 seconds in the future -3s # 3 seconds in the past +1h # 1 hour in the future etc.. Relative offsets must begin with a plus or minus symbol. The supported units are: s second m minute h hour d day (24 hours) M month (30 days) y year (365 days) If $t is an epoch time, then "time", "localtime", and "gmtime" will act as though the the current time (when "offset" was called) was actually at $t epoch seconds. Otherwise, the offset $t will be added to the times returned by these builtin subs. When $t is false, "time", "localtime", "gmtime" remain overridden, but their behavior resets to reflect the actual system time. When $t is omitted, nothing is changed, but "offset" returns the current additive offset (in seconds). Otherwise, its return value is the previous offset. "offset" may be called several times. However, The effect of multiple calls is NOT CUMULATIVE. That is: Time::Fake->offset("+1h"); Time::Fake->offset("+1h"); ## same as # Time::Fake->offset("+1h"); ## NOT the same as # Time::Fake->offset("+2h"); Each call to "offset" completely cancels out the effect of any previous calls. To make the effect cumulative, use the return value of calling "offset" with no arguments: Time::Fake->offset("+1h"); ... Time::Fake->offset( Time::Fake->offset + 3600 ); # add another hour reset Time::Fake->reset; Is the same as: Time::Fake->offset(0); That is, it returns all the affected builtin subs to their default behavior -- reporing the actual system time. KNOWN CAVEATS
Time::Fake must be loaded at "BEGIN"-time (e.g., with a standard "use" statement). It must be loaded before perl compiles any code that uses "time", "localtime", or "gmtime". Due to inherent limitations in overriding builtin subs, any code that was compiled before loading Time::Fake will not be affected. Because the system clock is not being changed, only Perl code that uses "time", "localtime", or "gmtime" will be fooled about the date. In particular, the operating system is not fooled, nor are other programs. If your Perl code modifies a file for example, the file's modification time will reflect the actual (not faked) time. Along the same lines, if your Perl script obtains the time from somewhere other than the affected builtins subs (e.g., "qx/date/"), the actual (not faked) time will be reflected. Time::Fake doesn't affect -M, -A, -C filetest operators in the way you'd probably want. These still report the actual (not faked) script start time minus file access time. Time::Fake has not been tested with other modules that override the time builtins, e.g., Time::HiRes. SEE ALSO
Time::Warp, which uses XS to fool more of Perl. AUTHOR
Time::Fake is written by Mike Rosulek <mike@mikero.com>. Feel free to contact me with comments, questions, patches, or whatever. COPYRIGHT
Copyright (c) 2008 Mike Rosulek. All rights reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.3 2008-01-17 Time::Fake(3pm)
All times are GMT -4. The time now is 03:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy