Search squid archive

RE: RE: coredump files location on Solaris 8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>
>Hi,
>
>I am no Solaris expert, however what about changing the overall system
>variable on Solaris for crash / core locations to per process core
>locations?
>
>http://www.c0t0d0s0.org/archives/4388-Less-known-Solaris-features-About
-crashes-and-cores-Part-3-Controlling-the-behaviour-of-the-dump-faciliti
es.html
>
>http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV2/p95.
html
>
>Best Regards,

this is what I am doing but I use squid with squidguard, ntlm, ldap and
seems the coreadm is not inherited so I get an average of 90 processes
running on each of my server meaning I made a little script to
automatically coreadm each pid but this is not always working so I
regularly have to coreadm processes gain and again ..... and this does
not explain me why :

* the current directory and the coredump_dir do not work ?
* I get regularly core dumps in the 20 minutes after the rotation
happening at midnight ?

>
>Alex
>
>On Fri, Jan 15, 2010 at 4:31 PM,  <vincent.blondel@xxxxxx> wrote:
>>
>>> Hello all,
>>>
>>> Can somebody say me how I can solve the way Squid stores coredump
>> files because I already tried to use coredump_dir and/or starting
Squid
>> from a dedicated directory but none of them seem to work on Solaris 8
>> because dump files are always put in /var/core ?
>>>
>>
>> nobody got this problem in the past ?
>>
>> many thks
>> Vincent
>
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
ING Belgium SA/nv -  Bank/Lender - Avenue Marnix 24, B-1000 Brussels, Belgium -  Brussels RPM/RPR - vat BE 0403.200.393 - BIC (SWIFT) : BBRUBEBB - Account: 310-9156027-89 (IBAN BE 45310-9156027-89). 
An insurance broker, registered with the Banking, Finance and Insurance Commission under the code number 12381A.

ING Belgique SA - Banque/Preteur, Avenue Marnix 24, B-1000 Bruxelles - RPM Bruxelles - tva BE 0403 200 393 - BIC (SWIFT) : BBRUBEBB - Compte: 310-9156027-89 (IBAN: BE 45310-9156027-89). 
Courtier d'assurances inscrit a la CBFA sous le no 12381A

ING Belgie nv - Bank/Kredietgever - Marnixlaan 24, B-1000 Brussel - RPR Brussel - btw BE 0403.200.393 - BIC (SWIFT) : BBRUBEBB - Rekening: 310-9156027-89 (IBAN: BE45 3109 1560 2789). 
Verzekeringsmakelaar ingeschreven bij de CBFA onder het nr. 12381A.
-----------------------------------------------------------------



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux