Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: How to give full access to output files created by .sh script run via crontab?
Top Forums Shell Programming and Scripting How to give full access to output files created by .sh script run via crontab? Post 302876833 by Chubler_XL on Tuesday 26th of November 2013 07:29:06 PM
Old 11-26-2013
Put umask 0 at the top of your script, then any new files your script creates with have full access.

You will still need to manually update the access on any existing files your script appends/modifies.
This User Gave Thanks to Chubler_XL For This Post:
Jeet1982
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

output from crontab run

Hi, I am trying to schedule a job in linux through the crontab command.My script actually does some text processing and echoes some output.My cron scheduler is working fine,but the output messages(echoes from script) is mailed to my mail account(in unix -/var/local/mail).Is it not possible... (0 Replies)
Discussion started by: DILEEP410
0 Replies

2. Shell Programming and Scripting

Routine doesn't give output when executed in crontab

I have a script running in the crontab that gets data from a database every hour. Now I would like to execute a fortran routine to process the data in some way, after getting it and saving it locally. I have added the following commands to my script: set convert =... (1 Reply)
Discussion started by: SharkM
1 Replies

3. Shell Programming and Scripting

Compare 2 files and give uniq output

Hi , Just to find out a way to compare these 2 files and give unique output. For eg: 1.txt contains 1 2 3 4 5 6 -------------------------------------- 2.txt contains 1 2 6 8 (1 Reply)
Discussion started by: rauphelhunter
1 Replies

4. Red Hat

ls command to give full path to files

How can i perform a ls or other command to list the full paths of files from a ls? Looked through the man page for ls, no luck $ cd /tmp/ $ ls -l total 6 drwx------ 2 root root 4096 Nov 7 2008 keyring-7b5rMv drwx------ 2 bcr bcr 4096 Dec 7 2007 keyring-cGhir8 $ I'd be looking for... (1 Reply)
Discussion started by: brendan76
1 Replies

5. Shell Programming and Scripting

perl script to check if empty files are created and delete them and run a shell script

I have a local linux machine in which the files are dumped by a remote ubuntu server. If the process in remote server has any problem then empty files are created in local machine. Is there any way using perl script to check if the empty files are being created and delete them and then run a shell... (2 Replies)
Discussion started by: hussa1n
2 Replies

6. Shell Programming and Scripting

Different output when run from crontab

Hi, I have a script which checks to see if an app is running and will restart it if it is not. For some reason when I run it from the crontab it always says it is not running. The script is as follows: - #!/bin/sh # # The following script will look for the PID of SickBeard and output... (15 Replies)
Discussion started by: simpic
15 Replies

7. Shell Programming and Scripting

awk: too many output files created from while loop

I am using awk to read lines from a CSV file then put data into other files. These other files are named using the value of a certain column. Column 7 is a name such as "att" or "charter" . I want to end up with file names with the value of column 7 appended to them, like this: ... (5 Replies)
Discussion started by: dodgerfan78
5 Replies

8. Shell Programming and Scripting

How to give password at run time in a shell script?

hi, how can i pass a password automatically when a shell script is running. i have shell script(runscript.sh) which call another shell script inside it as a different user. runscript.sh contains su - nemo -c "/bin/main_script.sh" but when i execute "runscript.sh" it try to run... (7 Replies)
Discussion started by: Little
7 Replies

9. Shell Programming and Scripting

Why my git command has no output in crontab but works well run this script manually?

cat /home/lyang001/update.sh #!/bin/sh #shopt -s expand_aliases HOME_DIR=/home/lyang001/updates UPDATE_MAIL=${HOME_DIR}/updates.mail rm $UPDATE_MAIL -rf cd $HOME_DIR/wr-kernel git log --no-merges --since="20 day ago" --name-status --pretty=format:"%an %h %s %cd" origin/WRLINUX_5_0_1_HEAD >>... (2 Replies)
Discussion started by: yanglei_fage
2 Replies

10. Shell Programming and Scripting

Script fails to run properly when run from CRONTAB

Hello all, I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly. My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Discussion started by: rusman
12 Replies

LEARN ABOUT MOJAVE

update-rc.d

INVOKE-RC.D(8)                                                   Debian GNU/Linux                                                   INVOKE-RC.D(8)

NAME

       invoke-rc.d - install and remove System-V style init script links

SYNOPSIS

       update-rc.d [-f] name remove

       update-rc.d name defaults

       update-rc.d name defaults-disabled

       update-rc.d name disable|enable [ S|2|3|4|5 ]

DESCRIPTION

       update-rc.d updates the System V style init script links /etc/rcrunlevel.d/NNname whose target is the script /etc/init.d/name.  These links
       are run by init when it changes runlevels; they are generally used to start and stop system services such as daemons.  runlevel is  one  of
       the  runlevels  supported  by init, namely, 0123456789S, and NN is the two-digit sequence number that determines where in the sequence init
       will run the scripts.

       This manpage documents only the usage and behaviour of update-rc.d.  For a discussion of the System V style init script arrangements please
       see init(8) and the Debian Policy Manual.

INSTALLING INIT SCRIPT LINKS

       update-rc.d requires dependency and runlevel information to be provided in the init.d script LSB comment header of all init.d scripts.  See
       the insserv(8) manual page for details about the LSB header format.

       When run with the defaults option, update-rc.d makes links named /etc/rcrunlevel.d/[SK]NNname that point to  the  script  /etc/init.d/name,
       using runlevel and dependency information from the init.d script LSB comment header.

       When  run  with  the  defaults-disabled  option,  update-rc.d  makes  links  named  /etc/rcrunlevel.d/KNNname  that  point  to  the  script
       /etc/init.d/name, using dependency information from the init.d script LSB comment header.  This means that the init.d script will  be  dis-
       abled (see below).

       If  any  files named /etc/rcrunlevel.d/[SK]??name already exist then update-rc.d does nothing.  The program was written this way so that it
       will never change an existing configuration, which may have been customized by the system administrator.  The  program  will  only  install
       links if none are present, i.e., if it appears that the service has never been installed before.

       Older  versions of update-rc.d also supported start and stop options.  These options are no longer supported, and are now equivalent to the
       defaults option.

       A common system administration error is to delete the links with the thought that this will "disable" the service,  i.e.,  that  this  will
       prevent  the service from being started.  However, if all links have been deleted then the next time the package is upgraded, the package's
       postinst script will run update-rc.d again and this will reinstall links at their factory default locations.  The correct  way  to  disable
       services is to configure the service as stopped in all runlevels in which it is started by default.  In the System V init system this means
       renaming the service's symbolic links from S to K.

       The script /etc/init.d/name must exist before update-rc.d is run to create the links.

REMOVING SCRIPTS

       When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories  to  the  script  /etc/init.d/name.
       The script must have been deleted already.  If the script is still present then update-rc.d aborts with an error message.

       update-rc.d  is  usually  called  from  a  package's  post-removal  script  when that script is given the purge argument.  Any files in the
       /etc/rcrunlevel.d directories that are not symbolic links to the script /etc/init.d/name will be left untouched.

DISABLING INIT SCRIPT START LINKS

       When run with the disable [ S|2|3|4|5 ] options, update-rc.d modifies existing runlevel links for the script /etc/init.d/name  by  renaming
       start links to stop links with a sequence number equal to the difference of 100 minus the original sequence number.

       When  run  with  the enable [ S|2|3|4|5 ] options, update-rc.d modifies existing runlevel links for the script /etc/init.d/name by renaming
       stop links to start links with a sequence number equal to the positive difference of current sequence number minus 100, thus  returning  to
       the original sequence number that the script had been installed with before disabling it.

       Both  of  these  options  only  operate  on start runlevel links of S, 2, 3, 4 or 5. If no start runlevel is specified after the disable or
       enable keywords, the script will attempt to modify links in all start runlevels.

OPTIONS

       -f     Force removal of symlinks even if /etc/init.d/name still exists.

EXAMPLES

       Insert links using the defaults:
          update-rc.d foobar defaults

       The equivalent dependency header would have start and stop dependencies on $remote_fs and $syslog, and start in runlevels 2-5 and  stop  in
       runlevels 0, 1 and 6.

       Remove all links for a script (assuming foobar has been deleted already):
          update-rc.d foobar remove

       Example of disabling a service:
          update-rc.d foobar disable

       Example of a command for installing a system initialization-and-shutdown script:
          update-rc.d foobar defaults

       Example of a command for disabling a system initialization-and-shutdown script:
          update-rc.d foobar disable

BUGS

       See http://bugs.debian.org/sysv-rc.

FILES

       /etc/init.d/
              The directory containing the actual init scripts.

       /etc/rc?.d/
              The directories containing the links used by init and managed by update-rc.d .

       /etc/init.d/skeleton
              Model for use by writers of init.d scripts.

SEE ALSO

       Debian Policy Manual,
       /etc/init.d/skeleton,
       insserv(8),
       sysv-rc-conf(8),
       bum(8),
       init(8)

AUTHOR

       Ian Jackson, Miquel van Smoorenburg

       Licence: GNU Public Licence v2 or Later (GPLv2+)

COPYRIGHT

       2001 Hernique Holschuh

14 November 2005                                                                                                                    INVOKE-RC.D(8)
All times are GMT -4. The time now is 01:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy