[IRCServices Coding] Crontab Script

Elijah admin at nevernet.net
Sun May 26 01:36:48 PDT 2002


How many times are we going to see this same message?

-----Original Message-----
From: ircservices-coding-admin at ircservices.za.net
[mailto:ircservices-coding-admin at ircservices.za.net] On Behalf Of
VisionOfHell at aol.com
Sent: Sunday, May 26, 2002 9:32 AM
To: ircservices-coding at ircservices.za.net
Subject: [IRCServices Coding] Crontab Script


The last time I wrote wrt the my crontab script you stated that it was 

my script that was faulty.

I am now using yours and am still getting the same results.

Basically I set the script and put a path to it in the crontab.

Every ten minutes I not only get an email stating services is starting
but I 
get the expected error in irc stating that it is cancelling the new link
as 
it already exists.

I then look in /lib and find that the .pid file has disappeared (it was
there 


when services started).

All I can think is that this element of the config is wrong:

# RunGroup <group>  [OPTIONAL]
#     Specify the group which Services should run as.  <group> can be  
#     either a group name or an equals sign ("=") followed by a group
ID. 
#     If not specified, Services will use the group ID it is started
with.
#     Note that Unix setgid permission on the executable file will do
the
#     same thing, but the setgid permission bit is cleared whenever the
#     file is modified, while this setting will always be used (if the
#     system permits it) when Services is started.

#RunGroup       ice
#RunGroup       =65534    # A common value for the "nogroup" group

# Umask <umask>  [RECOMMENDED]
#     Sets the umask (file creation mask) for Services.  This mask is
#     applied to all data files created by Services, including database
#     files (which are recreated on every database update) and the
process
#     ID file (PIDFile, below), and indicates which file permission bits
#     are NOT to be set on those files as an octal value.  Common values

#     are given in the examples below.  If not specified, the umask in
#     place when Services is started will be used.

#Umask          077     # Disallows access to all but file owner
                        #    (recommended when RunGroup is not set)
#Umask          007     # Allows access to members of file group as well
                        #    (recommended when RunGroup is set)

I have tried various combinations of the above to no avail.

Any help or advice would be much appreciated :)
------------------------------------------------------------------
To unsubscribe or change your subscription options, visit:
http://www.ircservices.za.net/mailman/listinfo/ircservices-coding