G'day again... Actually, I want the PID for neither of the reasons you've said. Rather, I'm using the PID and the date/time as a unique identifier to a database row. The main contents of the row could occur more than once in the table I'm working with - however we want to link this exact row with rows in other tables in the database. Initially I thought about using the date/time as an identifier (which I was storing anyway), but remembered that two instances of the script could be running concurrently, so decided to incorporate the PID to ensure uniqueness.
Regards, Michael S. E. Kraus Software Developer/Technical Support Specialist Wild Technology Pty Ltd [EMAIL PROTECTED] ________________________________ ABN 98 091 470 692 Level 4 Tiara, 306/9 Crystal Street, Waterloo NSW 2017, Australia Telephone 1300-13-9453 | Facsimile 1300-88-9453 http://www.wildtechnology.net The information contained in this email message and any attachments may be confidential information and may also be the subject of client legal - legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. This email and any attachments are also subject to copyright. No part of them may be reproduced, adapted or transmitted without the written permission of the copyright owner. If you have received this email in error, please immediately advise the sender by return email and delete the message from your system. -----Original Message----- From: Robert Collins [mailto:[EMAIL PROTECTED] Sent: Monday, 18 October 2004 11:33 AM To: Michael Kraus Cc: Glen Turner; [EMAIL PROTECTED] Subject: RE: [SLUG] Maximum process ID On Mon, 2004-10-18 at 11:06 +1000, Michael Kraus wrote: > G'day... > > Whilst this discussion is pretty great - I would like to note that the > practical purpose of knowing the size of a PID is so that I can store > the current processes' PID in an MySQL database, and the process is a > Perl script. The key element is why do you need the pid? There is usually only two good reasons to know a process's pid: 1) to kill it 2) to tell it to cleanly shutdown. And then you still need to check its the same command line you thought it was. Do you want the pid for one of those reasons, or another?... Is it so that you know what the current processs? (so what happens when it dies and is replaced, with the same pid, with another process - perhaps even the same script again). Is it for auditing? What happens if the perl script runs twice at once ? Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
