TRFC Logs? Program RBDMOIND..

Hi All,
Is there any way to check the tRFC logs? A TID corresponding to an idoc was stucked in tRFC queue for long and then it disappeared.
Is there any way I can check whether the TID was deleted or it got processed successfully?
The corresponding idoc is in status 12 now....Is it possible that idoc moved to status 12 from status 03 even if TID was deleted?
What does program RBDMOIND actually do and how does this affect the status of idoc?

Hi All,
Got answer to my question partly..
Idoc can go to status 12 even if corresponding TID has been deleted from tRFC queue. It's where RBDMOIND come to play...
RBDMOIND pick up all the status 03 idoc for a specific date and compare whether their TIDs are in tRFC queue. If TID is present then status remains as 03 and if TID is not found that then status of corresponding idoc is changed to 12 (irrespective of whether idoc was processed or deleted).
But still if anyone know any way to check tRFC logs, it will be helpful.
Regards,
Pawan Purohit

Similar Messages

Why does my data logging program slow down after a while?

A data logging program created with Labview 5.1. Slows down after a few weeks and creates files in the Temp. directory.Computer is Siemens Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also using Solartron Dig. probes and Fieldpoint units.

Any chance that you are using Win 95/88/ME? Those OS's have well documented
memory leaks which will consume all your available memory if an application
is run long enough. Also there are some issues of memory management within
LabView in the allocation of memory.
The solution to the first is to switch to WinNT/2K. The second will be much
more difficult.
On Thu, 22 Feb 2001 03:19:12 -0800 (PST), Freek wrote:
>A data logging program created with Labview 5.1. Slows down after a
>few weeks and creates files in the Temp. directory.Computer is Siemens
>Scenic pro 124 MB ram and AT-MIO-16XE50 Data acquisition board. Also
>using Solartron Dig. probes and Fieldpoint units.
===========================================================================
SolidW
orks Research Partner National Instruments Alliance Member
Christopher Dubea Phone: (504) 847-2280
Vice President of Engineering Fax: (504) 847-2282
Moving Parts L.L.C. email: [email protected]
P. O. Box 6117 URL: http://www.movingpart.com
Slidell, LA 70469-6117

Characteristics Change Log: Program RCCLUKA2 ??

Hi,
I am looking for a table or method to document changes made to the characteristics of DMS docs. Can you advise if there is a table similar to DRAP that displays this or if there is another method possible?
EDIT: I have searched the forum and found a potential solution to my problem [Re: Document Management - Enhancem. to log changes to Classification Character.;
However I am concerned what the results of running the program RCCLUKA2 retroactively will be as there is already DMS docs in my system.
Can anyone please advise?
Thank you
Edited by: goldencleric on Nov 19, 2010 3:38 PM

Hi,
in the mentioned older thread have you also read through the link for Classification Change documents:
http://help.sap.com/erp2005_ehp_02/helpdata/en/24/4764e4416711d189ec0000e81ddfac/frameset.htm
The execution of the report will change the way the classification data is stored. After running the report the classification values are stored in table INOB and with the value in field CUOBJ the INOB table entries are linked to entries in table AUSP.
Please see also the SAP notes 942691 and 943559.
Best regards,
Christoph

Labview logging program crash windows after 2 days

I am using Labview 8.0, and running the executable the program. What this program does is that it acquires data and then writes to hard drive. Each set of data is small but it writes also every second. It will create a new file every day so the file does not get too big.
After 2~3 days running, it crash windows. I think it somehow used up all the resource so the windows would not even response any more. And we need to run this program continually for at least one month.
So is this a memory leak problem of the executable program generated by Labview app builder? or could that be Labview does not release memory after it writes data to the file, and eventually used up the resource?
any suggestions?
Thanks

It is on a laptop with win xp, 1GB Ram. each data is only 40~50 bytes. The concatenate strings does not duplicate in memory, right? what about build path and open file? Do I need to close the file inside the loop? It is a very small program so I attached a screen capture here.
I am going to let it restart again and check memory usage tomorrow.
Thanks,
Attachments:
screen shot.gif ‏36 KB

How to use Prelude just as a logging program?

During shooting we have to work very fast and just get the media off the camera cards ASAP via the shortest route i.e. directly store on a drive using a card reader and no intermediate software like Prelude, which I suspect would be too slow for our needs on a shoot day in any case.
However, I would then later, when I have time, like the organisation and compatability that Prelude can bring for editing in Premiere Pro. I can do this if I import the already ingested material from the drives, but if I do this Prelude then makes another new copy on the the drives of all the media - this wastes time and also causes massive storage problems with formats like Red 4K.
Is there a a way to use the logging and comment facility ONLY in Prelude so that clips can be organised but not re-copied onto the drives?

This is what the on-line chat help person thinks - no go it seems!
John: So do you think it is possible just to log without re-ingesting the media
Vaibhav: No
Vaibhav: you have to ingest file and then would be able to log
John: yes but I have already ingested them and do not want to double the storage I would require or the time it would take to re-ingest - just want to add comments to the files
Vaibhav: but if you want to log and comment ingesting is must
John: Ah then that is a failing in the software - I have posted it on the forum - thanks anyway
Vaibhav: you are welcome
Vaibhav: you can fill in the feature request form
John: where is that?
Vaibhav: one minute
Vaibhav:https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
John: thanks
Vaibhav: Thank you for contacting Adobe. Good Bye.

Options to log program crashes/errors for deployed apps

I've done a bunch of reading on the topic and am getting mixed information. In my case, I have a released application running on four Win7 targets. Ocassionally, I'm getting some application crashes. I am certain there is some firmware-level problems going on with my custom IO board as well, but I need some tools to troubleshoot why the CVI app is crashing.
I've seen recommenation to try the Windows Event Viewer, Dr. Watson (for WinXP targets), etc, but these are pretty generic.
This is a good thread, but didn't go anywhere.
And then there's the article on the ConfigCVILogging tool. This seems promising too, but it's unclear to me how I can package that EXE with my app distribution. Also, what setup do I need in my app so that it is aware of the CVILogging EXE?
Ideas?

Hi Electrolund,
It would be helpful if you could post screenshots of any errors you are seeing when these crashes happen. Could you describe how the applications crash exaclty? Does it always happen after a certain input or action or is it pretty much random? Does it happen in the same way on all 4 test computers? I think you are a little confused about the way that ConfigCVILogging tool works. I believe the way it works is that any time the run time engine DLLs are called that application will know about it and make entries to the log. So running your executable should visible to that process.
Regards,
Basil
Applications Engineering
National Instruments

Temp logging programs ?

What nice temp monitoring/logging apps are there ? I've seen screenshots of apps that draw nice graphs...that way you'd see the "mean temp", not fluctuating highest temp (2-3C over normal max)

Never liked MBM, but does SpeedFan show a (graphical for example) LOG ? Showing correct current temp is not what I'm looking for, but "viewable cpu temp history" (while I play games etc)
EDIT ///
OK, found it, and it's seems to be exactly what I am looking for thx
Screenshots of SpeedFan: http://www.almico.com/sfscreenshots.php

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

SAP IDOC - XI - NON SAP IDOC (tRFC)

Hi all,
our scenario is as follows:
1) SAP ERP 2005 send an IDOC to XI (NW04S, 7.0)
2) XI dos nothing, just routing. So no mapping or stuff like that
3) XI should send the IDOc to a non SAP System via a tRFC (registered program id)
a) IDOC can be sent to XI and for test we introduced a file adapter. The IDOC is written to the file system successfully.
b) tRFC is registered connection test ok to the NON SAP System.
c) SLD is maintained with a NON SAP technical and a business system
d) Which adapter to use?
- IDOC Adapter (following error)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
<SAP:P1>BS_OS_N_SEEBURGER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service BS_OS_N_SEEBURGER cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- RFC Adapter (following error)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>P_OS_EBV_511158_RECEIVER,BS_OS_N_SEEBURGER</SAP:P1>
<SAP:P2>,BS_OS_OSQ_300,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
If I set the IDXNOALE the message is succesfully processed but not received by the NON SAP system which is connected to the same tRFC.
I do not know how to set this scenario, any ideas?
Thanks
BR Markus

Hi all,
at first thanks for the fast reply.
I do not use any kind of mapping, so the message should be prozessed through without any changes.
So two questions:
1) Where to set the exactly once, ...?
2) Where to set the return paramaters?
Inside the SLD the logical system name is configured. I had the settings maintained like Sergio wrote it.
I changed my configuration to the following:
- No Party
- No Business System
- Creation of a Business Service with the same Logical System as configured in the Bus of SLD
-> Everything works all right
So I created the scenario with No Party but again with the Bus and everything was all right, so.
I had any error in the first scenario but I do not know which one, too many thing changed during the process of problem solving.
Thanks a lot anyway.
BR Markus

Ale customization through executable programs

i have followed the following steps to customize ale for message type MATMAS
create logical systems EP800, EP810
assign logical systems to clients
create modelview --> save
add message type --> save
generate partner profiles --> execute
here iam getting an error saying that
   Port could not be created
   RFC destination EP810 not specified for system EP810
Enter the RFC destination and restart the generation
to solve this i have manually created port in we21.
but still uam getting the same error.
how to procede now

Hai Lavanya
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

Program exit code 259 in SCCM Cllient

Hi,
I am getting Error "Program exit code 259" in Execmgr.log while installing symantec backup tool on sccm client.
Execmgr.log:
Execution Request for package C010194B program Symantec Backup Exec System Recovery v8.5.3.314-0 state change from Running to NotifyExecution execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Checking content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.System for use execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.System execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Executing program as a script execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\loader.EXE" /s CM_DSLID=002FDA execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Command line = "C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\loader.EXE" /s CM_DSLID=002FDA, Working Directory = C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\ execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Created Process for the passed command line execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "N0120AAD";
ClientID = "GUID:C7E780C0-72FE-4876-B3B3-ACC7E7AB5D71";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\C010194B.1.System\\loader.EXE\" /s CM_DSLID=002FDA";
DateTime = "20090826050952.320000+000";
MachineName = "WFSLUSLVA8DYW";
PackageName = "C010194B";
ProcessID = 3876;
ProgramName = "Symantec Backup Exec System Recovery v8.5.3.314-0";
SiteCode = "N02";
ThreadID = 448;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\C010194B.1.System\\";
execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Raised Program Started Event for Ad:N0120AAD, Package:C010194B, Program: Symantec Backup Exec System Recovery v8.5.3.314-0 execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)
Execution Manager timer has been fired. execmgr 8/26/2009 1:12:03 AM 2228 (0x08B4)
Program exit code 259 execmgr 8/26/2009 2:09:52 AM 5392 (0x1510)

<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="16:09:34.651+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1312">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="16:09:34.827+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1312">
<![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="16:09:34.842+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1413">
<![LOG[Software distribution agent was enabled]LOG]!><time="16:11:48.870+000" date="10-13-2009" component="execmgr" context="" type="1" thread="3804" file="execreqmgr.cpp:5969">
<![LOG[Policy arrived for parent package QQQ00009 program RAR]LOG]!><time="04:19:00.850+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="execreqmgr.cpp:6451">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramOfferReceivedEvent
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221900.962000+000";
    MachineName = "SCOM";
    ProcessID = 2824;
    SiteCode = "QQQ";
    ThreadID = 3668;
]LOG]!><time="04:19:00.976+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="event.cpp:525">
<![LOG[Policy arrived for parent package QQQ0000E program Setup]LOG]!><time="04:19:01.005+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="execreqmgr.cpp:6451">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramOfferReceivedEvent
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221901.016000+000";
    MachineName = "SCOM";
    ProcessID = 2824;
    SiteCode = "QQQ";
    ThreadID = 3668;
]LOG]!><time="04:19:01.017+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="event.cpp:525">
<![LOG[Requesting content from CAS for package QQQ00009 version 1]LOG]!><time="04:19:02.678+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="contentaccesshelper.cpp:138">
<![LOG[Successfully created a content request handle {E493064B-D93A-4FD2-83FF-886B4325A796} for the package QQQ00009 version 1]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="contentaccesshelper.cpp:216">
<![LOG[Program RAR change to state STATE_ADVANCED_DOWNLOAD content in progress]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1168" file="executionrequest.cpp:3670">
<![LOG[Execution Request for package QQQ00009 program RAR state change from NotExist to AdvancedDownload]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="executionrequest.cpp:488">
<![LOG[Mandatory execution requested for program RAR and advertisement QQQ20008]LOG]!><time="04:19:03.344+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert QQQ20008, program RAR, package QQQ00009]LOG]!><time="04:19:03.357+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="execreqmgr.cpp:3440">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistWaitingContentEvent
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221903.978000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    PackageVersion = "1";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 2964;
]LOG]!><time="04:19:03.983+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="event.cpp:525">
<![LOG[Successfully raised SoftDistWaitingContentEvent event for program RAR]LOG]!><time="04:19:03.985+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="executionrequest.cpp:2623">
<![LOG[Execution Request for package QQQ00009 program RAR state change from WaitingDependency to WaitingContent]LOG]!><time="04:19:03.985+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="executionrequest.cpp:488">
<![LOG[Requesting content from CAS for package QQQ0000E version 1]LOG]!><time="04:19:04.328+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="contentaccesshelper.cpp:138">
<![LOG[Successfully created a content request handle {1AEB98AA-58BE-428F-883A-936448A7AC88} for the package QQQ0000E version 1]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="contentaccesshelper.cpp:216">
<![LOG[Program Setup change to state STATE_ADVANCED_DOWNLOAD content in progress]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1280" file="executionrequest.cpp:3670">
<![LOG[Execution Request for package QQQ0000E program Setup state change from NotExist to AdvancedDownload]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="executionrequest.cpp:488">
<![LOG[Mandatory execution requested for program Setup and advertisement QQQ20011]LOG]!><time="04:19:04.483+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert QQQ20011, program Setup, package QQQ0000E]LOG]!><time="04:19:04.534+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="execreqmgr.cpp:3440">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistWaitingContentEvent
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221904.861000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    PackageVersion = "1";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 3460;
]LOG]!><time="04:19:04.871+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="event.cpp:525">
<![LOG[Successfully raised SoftDistWaitingContentEvent event for program Setup]LOG]!><time="04:19:04.877+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:2623">
<![LOG[Execution Request for package QQQ0000E program Setup state change from WaitingDependency to WaitingContent]LOG]!><time="04:19:04.877+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:488">
<![LOG[Content is available for program RAR.]LOG]!><time="04:19:08.813+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:4915">
<![LOG[CExecutionRequest::Service Windows Manager has allowed us to run.]LOG]!><time="04:19:08.859+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:3071">
<![LOG[Execution Request for package QQQ00009 program RAR state change from WaitingContent to NotifyExecution]LOG]!><time="04:19:08.859+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:488">
<![LOG[Notify user mandatory program RAR is about to run]LOG]!><time="04:19:08.893+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:3112">
<![LOG[Content is available for program Setup.]LOG]!><time="04:22:59.476+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:4915">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramWaitingForAnotherProgram
    AdvertisementId = "QQQ20011";
    BlockingPackageID = "QQQ00009";
    BlockingProgramName = "RAR";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013222259.546000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 864;
]LOG]!><time="04:22:59.551+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="event.cpp:525">
<![LOG[Successfully raised SoftDistProgramWaitingForAnotherProgram event for program Setup.]LOG]!><time="04:22:59.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:2899">
<![LOG[Execution Request for package QQQ0000E program Setup state change from WaitingContent to Ready]LOG]!><time="04:22:59.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:488">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:24:08.940+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="execreqmgr.cpp:5188">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:24:08.993+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="execreqmgr.cpp:5188">
<![LOG[Executing program "wrar380ru.exe" /s in Admin context]LOG]!><time="04:24:09.038+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionrequest.cpp:3277">
<![LOG[Execution Request for package QQQ00009 program RAR state change from Running to NotifyExecution]LOG]!><time="04:24:09.085+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionrequest.cpp:488">
<![LOG[Checking content location C:\Windows\system32\CCM\Cache\QQQ00009.1.System for use]LOG]!><time="04:24:09.172+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:1635">
<![LOG[Successfully selected content location C:\Windows\system32\CCM\Cache\QQQ00009.1.System]LOG]!><time="04:24:09.173+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:1703">
<![LOG[GetFileVersionInfoSize failed for file C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe, error 1813]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1788" file="executioncontext.cpp:119">
<![LOG[Executing program as a script]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionengine.cpp:103">
<![LOG[Successfully prepared command line "C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe" /s]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:523">
<![LOG[Command line = "C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe" /s, Working Directory = C:\Windows\system32\CCM\Cache\QQQ00009.1.System\]LOG]!><time="04:24:09.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:284">
<![LOG[Created Process for the passed command line]LOG]!><time="04:24:09.300+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:407">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramStartedEvent
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    CommandLine = "\"C:\\Windows\\system32\\CCM\\Cache\\QQQ00009.1.System\\wrar380ru.exe\" /s";
    DateTime = "20091013222409.308000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 1788;
    UserContext = "NT AUTHORITY\\SYSTEM";
    WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\QQQ00009.1.System\\";
]LOG]!><time="04:24:09.318+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="event.cpp:525">
<![LOG[Raised Program Started Event for Ad:QQQ20008, Package:QQQ00009, Program: RAR]LOG]!><time="04:24:09.321+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:523">
<![LOG[Program exit code 0]LOG]!><time="04:24:12.399+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="scriptexecution.cpp:547">
<![LOG[Looking for MIF file to get program status]LOG]!><time="04:24:12.399+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionstatus.cpp:282">
<![LOG[Script for Package:QQQ00009, Program: RAR succeeded with exit code 0]LOG]!><time="04:24:12.401+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionstatus.cpp:259">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramCompletedSuccessfullyEvent
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013222412.410000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 3564;
    UserContext = "NT AUTHORITY\\SYSTEM";
]LOG]!><time="04:24:12.415+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="event.cpp:525">
<![LOG[Raised Program Success Event for Ad:QQQ20008, Package:QQQ00009, Program: RAR]LOG]!><time="04:24:12.419+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executioncontext.cpp:551">
<![LOG[Execution is complete for program RAR. The exit code is 0, the execution status is Success]LOG]!><time="04:24:12.419+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="execreqmgr.cpp:3908">
<![LOG[CExecutionRequest::Service Windows Manager has allowed us to run.]LOG]!><time="04:24:12.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:3071">
<![LOG[Execution Request for package QQQ0000E program Setup state change from Ready to NotifyExecution]LOG]!><time="04:24:12.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:488">
<![LOG[Notify user mandatory program Setup is about to run]LOG]!><time="04:24:12.558+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:3112">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:26:19.903+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3820" file="execreqmgr.cpp:5188">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:29:12.150+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3840" file="execreqmgr.cpp:5188">
<![LOG[Executing program Setup.exe in Admin context]LOG]!><time="04:29:12.161+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionrequest.cpp:3277">
<![LOG[Execution Request for package QQQ0000E program Setup state change from Running to NotifyExecution]LOG]!><time="04:29:12.173+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionrequest.cpp:488">
<![LOG[Checking content location C:\Windows\system32\CCM\Cache\QQQ0000E.1.System for use]LOG]!><time="04:29:12.196+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:1635">
<![LOG[Successfully selected content location C:\Windows\system32\CCM\Cache\QQQ0000E.1.System]LOG]!><time="04:29:12.196+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:1703">
<![LOG[Executing program as a script]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionengine.cpp:103">
<![LOG[Successfully prepared command line "C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\setup.exe"]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:523">
<![LOG[Command line = "C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\setup.exe", Working Directory = C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:284">
<![LOG[Created Process for the passed command line]LOG]!><time="04:29:12.395+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:407">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramStartedEvent
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    CommandLine = "\"C:\\Windows\\system32\\CCM\\Cache\\QQQ0000E.1.System\\setup.exe\"";
    DateTime = "20091013222912.413000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 1320;
    UserContext = "NT AUTHORITY\\SYSTEM";
    WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\QQQ0000E.1.System\\";
]LOG]!><time="04:29:12.423+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="event.cpp:525">
<![LOG[Raised Program Started Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="04:29:12.426+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:523">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:33:31.003+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="execreqmgr.cpp:5188">
<![LOG[Program exit code 259]LOG]!><time="06:29:13.174+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="scriptexecution.cpp:547">
<![LOG[Looking for MIF file to get program status]LOG]!><time="06:29:13.178+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executionstatus.cpp:282">
<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time="06:29:13.184+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executionstatus.cpp:232">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramExceededTime
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091014002913.196000+000";
    MachineName = "SCOM";
    MaximumTime = "120";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 2788;
]LOG]!><time="06:29:13.204+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="event.cpp:525">
<![LOG[Raised Program Exceeded Time Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executioncontext.cpp:945">
<![LOG[Execution is complete for program Setup. The exit code is 259, the execution status is Unknown Status]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="execreqmgr.cpp:3908">
<![LOG[A user has logged on.]LOG]!><time="10:24:37.257+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3644" file="execreqmgr.cpp:4522">
<![LOG[The logged on user is WER\admin]LOG]!><time="10:24:37.595+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3644" file="execreqmgr.cpp:4540">
<![LOG[A user has logged on.]LOG]!><time="15:55:34.833+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1708" file="execreqmgr.cpp:4522">
<![LOG[The logged on user is WER\admin]LOG]!><time="15:55:35.776+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1708" file="execreqmgr.cpp:4540">

Logs for BIAR command line tool XI3.0

Hi,
Will there be any log files generated by the BIAR command line tool, when we try to export to a BIAR file?
Thanks,
Ashok Kumar M

Information regarding the import can be found in the following locations:
- Program Files\Business Objects\BusinessObjects 11.5\Logging
- Program Files\Business Objects\BusinessObjects 11.5\win32_x86
- Windows Event Viewer " If an error was encountered during import, the information will often be found here.
To generate more logs during the import:
Create a shortcut of the Import Wizard executable. The executable is found in <installation directory>:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32_x86.
Right-click the new shortcut. Click Properties.
Click the Shortcut tab. Add "trace at the end of the Target command line as follows:
"C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32-x86\ImportWiz.exe" -trace
Click OK.
When starting the import process, use this new shortcut instead of the previous one to start a trace. The resulting logs will reside in <installation directory>: \Program Files\Business Objects\BusinessObjects 11.5\Logging.
Caroline

Programming on palm using a database

Hi,
I have recently been able to create a small Midlet program with J2ME and load it up onto my palm and run it.
The program is a work log program
My question is:
Is there a way to store my logs on the palm in a database file and view them when I need to. I have not been able to find a way to do it. There has got to be a way to do it because I see other applications on the palm that do it.
Please help
Thanks
Bob

Post this over on the K virtual machine forum

Key logging software doesnt capture passwords

I'm trying to implement keystroke logging software on my laptop. However, a number of demo's I've used do not seem to capture password fields. I think this may be a feature of Safari, but I'm not sure.
Example - Accessing Hotmail from Safari; the email account name is captured but the password is not.
This seems to be a constant problem, independent of the key logging program used.
Can any one help me out?
Regards.
Macbook Pro Mac OS X (10.4.6)

Hi
Welcome to Apple Discussions
Browsers, such as Safari, "remember" user name/passwords unless a specific website is coded by the Developer to override this feature. This is done for security purposes.
3rd party - SAFT offers a number of very useful features including one to circumvent this override. Works for most sites, such as Yahoo Mail. Does not work for more sophisticated log-in areas such as Banks/Credit Card companies employing the recent "sitesecure".

Suggestion for default arch logging behavior

Okay let me throw this out there and see what comes back...
Every Linux distribution I have used (apart from arch) has a boot log file enabled by default, or provides a simple Yes/No flag to turn the feature on.
Arch does not. Moreover, I have searched the forums and posted a question or two myself about the topic. No one seems to know the answer, and a lot of responses seem to indicate that, amongst the arch community, the possibility of a boot log file is treated like: a) something that no one in their right mind would want, or b) something that maybe, might be useful, but that no one can figure out how to implement.
What is this? What is going on? Arch has a bootlogd binary in /sbin/. Presumably there is no reason why it won't actually work, but no one seems to know where to put the call to the binary, or why they would put it there.
This seems like an easy-to-add feature that a developer or moderator (anyone who really knows the system layout well) could make the default for future installs. It just makes a text file that is a) not large, and b) can be very useful at times.
So how about it? Why not make this part of the default arch logging set up? (and of course explain what you did that worked.)

tomk:
Sorry to disclose my ignorance, but I'm not sure how to do that.
What I have been doing though is trying to see in more detail how it is done on a debian system which I have access to. Here is what I've learned so far:
There are not that many references to bootlogd on the system, so it might be possible (for me) to track down what is going on:
root@wave32p:/etc# locate bootlogd
/etc/default/bootlogd
/etc/init.d/bootlogd
/etc/init.d/stop-bootlogd
/etc/init.d/stop-bootlogd-single
/sbin/bootlogd
/usr/share/man/man8/bootlogd.8.gz
1) "/etc/default/bootlogd" must be edited (trivially) such that a "No" becomes a "Yes" -- this seems like just a master switch.
2) the man files are exactly the same on the two systems, and the output of "/sbin/bootlogd -v" is the same on the two systems, however the size of the bootlogd binary itself is not the same on both systems (larger on debian64 system). not sure what to make of that, but it is not what I was hoping to see.
3) the script "/etc/init.d/bootlogd" runs with (eg.) a "start/stop" flag, the same as most "functions" under arch that have scripts associated with them.
4) it would seem that I have to grind my way through the above script if I'm going to make any progress. I'm doing that in my spare time at the moment, though it's a challenge since it's been a few years since I've written bash scripts on a regular basis. FYI, here is the /etc/init.d/bootlogd script verbatim (additional note: the option -r (below) is supported on the arch version of the bootlogd binary, but the -c option does not seem to be...interesting? Here is the man page entry for -c: "Attempt to write to the logfile even if it does not yet exist. Without this option, bootlogd will wait for the logfile to appear before attempting to write to it. This behavior prevents
bootlogd from creating logfiles under mount points."):
#! /bin/sh
### BEGIN INIT INFO
# Provides: bootlogd
# Required-Start: mountdevsubfs
# X-Start-Before: hostname keymap keyboard-setup procps pcmcia hwclock hwclockfirst hdparm hibernate-clean
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Start or stop bootlogd.
# Description: Starts or stops the bootlogd log program
# which logs boot messages.
### END INIT INFO
PATH=/sbin:/bin # No remote fs at start
DAEMON=/sbin/bootlogd
[ -x "$DAEMON" ] || exit 0
NAME=bootlogd
DESC="boot logger"
BOOTLOGD_OPTS="-r -c"
[ -r /etc/default/bootlogd ] && . /etc/default/bootlogd
. /lib/init/vars.sh
. /lib/lsb/init-functions
# Because bootlogd is broken on some systems, we take the special measure
# of requiring it to be enabled by setting an environment variable.
case "$BOOTLOGD_ENABLE" in
[Nn]*)
exit 0
esac
# Previously this script was symlinked as "stop-bootlogd" which, when run
# with the "start" argument, should stop bootlogd. Now stop-bootlogd is
# a distinct script, but for backward compatibility this script continues
# to implement the old behavior.
SCRIPTNAME=${0##*/}
SCRIPTNAME=${SCRIPTNAME#[SK]??}
ACTION="$1"
case "$0" in
*stop-bootlog*)
[ "$ACTION" = start ] && ACTION=stop
esac
case "$ACTION" in
start)
# PATH is set above
log_daemon_msg "Starting $DESC" "$NAME"
if [ -d /proc/1/. ]
then
umask 027
start-stop-daemon --start --quiet --exec $DAEMON -- \
$BOOTLOGD_OPTS
ES=$?
else
$DAEMON $BOOTLOGD_OPTS
ES=$?
fi
log_end_msg $ES
stop)
PATH=/bin:/sbin:/usr/bin:/usr/sbin
log_daemon_msg "Stopping $DESC" "$NAME"
start-stop-daemon --oknodo --stop --quiet --exec $DAEMON
ES=$?
sleep 1
log_end_msg $ES
if [ -f /var/log/boot ] && [ -f /var/log/boot~ ]
then
[ "$VERBOSE" = no ] || log_action_begin_msg "Moving boot log file"
# bootlogd writes to boot, making backup at boot~
cd /var/log && {
chgrp adm boot || :
savelog -q -p -c 5 boot \
&& mv boot.0 boot \
&& mv boot~ boot.0
ES=$?
[ "$VERBOSE" = no ] || log_action_end_msg $ES
fi
restart|force-reload)
/etc/init.d/bootlogd stop
/etc/init.d/bootlogd start
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 3
esac

TRFC Logs? Program RBDMOIND..

Similar Messages

Maybe you are looking for