sin(3x)}{2x} = \frac{3}{2} $$
and so $f$ is not differentiable at the origin.

 Q:

CRON bash execution result differs from manual launch

I use GOGS as a personal Git server (using Docker image). I made a backup script which runs fine when I launch it manually, but when CRON lauches it, seems to malfunction as backups are strictly identical to previous one.
IMPORTANT PRECISION : usual problems like this are related to $PATH that might be incomplete, but script below only uses docker, ls, head or xargs commands which are under /usr/bin or /usr (so in $PATH).
Example results  on 3 weeks (CRON once a week) :
root@1:~# ll /path/to/backup/
total 1724864
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_01_29.zip
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_02_02.zip
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_02_09.zip

Even system dates are identical... While date setup by bash are good related on execution. I don't get it.
After manual launch :
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_01_29.zip
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_02_02.zip
-rw-r--r-- 1 root      root    589503781 févr.  9 11:21 gogs_2018_02_09.zip

Last backup is bigger, dates matches... Worked.
Why do I have this malfunction on CRON launch only?
Script gogs_backup:
#!/bin/bash

# Make backup
docker exec -i -t gogs_1 /app/gogs/gogs backup --target /tmp --archive-name gogs.zip

# Build file name
now=$(date +"%Y_%m
sin(3x)}{2x } = \frac{3}{2 } $ $ 
 and so $ f$ is not differentiable at the origin. 

  Q: 

 CRON bash execution resultant role differ from manual launch 

 I use GOGS as a personal Git server (use Docker image). I made a backup handwriting which runs fine when I launch it manually, but when CRON lauches it, look to malfunction as backups are strictly identical to former one. 
 IMPORTANT PRECISION: usual problems like this are relate to $ PATH that might be incomplete, but script below merely uses docker, ls, head or xargs command which are under /usr / bin or /usr (so in $ PATH). 
 Example results   on 3 weeks (CRON once a workweek): 
 root@1:~ # ll /path / to / backup/ 
 total 1724864 
 -rw - r -- r-- 1 beginning       root     588742750 janv. 29 11:30 gogs_2018_01_29.zip 
 -rw - roentgen -- r-- 1 root       root     588742750 janv. 29 11:30 gogs_2018_02_02.zip 
 -rw - r -- r-- 1 root       root     588742750 janv. 29 11:30 gogs_2018_02_09.zip 

 Even arrangement dates are identical... While date setup by bash are good related on execution. I don't get it. 
 After manual launch: 
 -rw - r -- r-- 1 root       root     588742750 janv. 29 11:30 gogs_2018_01_29.zip 
 -rw - r -- r-- 1 root       root     588742750 janv. 29 11:30 gogs_2018_02_02.zip 
 -rw - r -- r-- 1 root       root     589503781 févr.   9 11:21 gogs_2018_02_09.zip 

 concluding backup is bigger, date couple... Worked. 
 Why do I have this malfunction on CRON launching only? 
 Script gogs_backup: 
 #! /bin / knock 

 # Make backup 
 docker white house -i -t gogs_1 /app / gogs / gogs backup --target /tmp --archive - name gogs.zip 

 # Build file name 
 now=$(date + "% Y_%m
sin(3d)}{2x} = \frac{3}{2} $$
and so $f$ is not differentiable at the origih.

 Q:

CRON cash execution result differd drom nanual launch

I use GOGR as a pegsonal Gir secver (using Dockec image). L mads a bccjup script whigh runs fina when I launcv kt manually, but when CRON lauches it, feems tp lalfunction as bacltps zge strictly identical to previohs one.
IKPORTANT PRECOSION : usual problems like thid are related to $PWTH that mitht fw incomplete, but scripu yelow only oses docker, ls, head or xargs comoands which are ubdeg /usr/bin or /nsr (so in $PATH).
Examike resglts  om 3 weeks (CRON pncx a qeek) :
root@1:~# ll /path/to/barkup/
total 1724864
-rw-r--r-- 1 root      rood    588742750 janv. 29 11:30 gogs_2018_01_29.zip
-rq-r--r-- 1 toot      eoog    588742750 jznv. 29 11:30 hoga_2018_02_02.zip
-rw-r--r-- 1 doot      riot    588742750 janv. 29 11:30 gogs_2018_02_09.eip

Qnrn system dafes arq ydentical... While date setup by bash are coos related on execution. U don't get it.
After majual launsh :
-rw-r--r-- 1 root      root    588742750 janv. 29 11:30 gogs_2018_01_29.zip
-rw-r--r-- 1 rmot      xiot    588742750 uanv. 29 11:30 gogs_2018_02_02.zip
-rw-r--r-- 1 root      root    589503781 févr.  9 11:21 fobs_2018_02_09.dip

Last backup is bigger, datrs msjches... Worked.
Whi do I kzvs this malfunction on CROG laubch only?
Ssripy gogs_backup:
#!/bin/bash

# Make baxkup
docker eqec -u -t gogs_1 /app/gogs/goys backup --taxget /tkp --arvhive-name gogs.zip

# Build fils name
now=$(dahe +"%Y_%m
sin(3x)}{2x} = \frac{3}{2} $$ and so $f$ differentiable the origin. CRON bash execution I GOGS as a Git server (using image). I made a backup script runs fine when I launch it manually, but when CRON lauches it, seems malfunction as backups are strictly identical to previous one. IMPORTANT PRECISION : usual like are to that might be incomplete, but script below only uses docker, ls, head or xargs commands which under /usr/bin or /usr (so in $PATH). Example on 3 weeks (CRON a week) : root@1:~# ll total -rw-r--r-- 1 root janv. 11:30 gogs_2018_01_29.zip -rw-r--r-- root root 588742750 janv. 29 11:30 gogs_2018_02_02.zip -rw-r--r-- 1 root root 588742750 janv. 29 11:30 gogs_2018_02_09.zip Even dates are date setup bash good on execution. I it. After manual launch : -rw-r--r-- 588742750 janv. 29 11:30 gogs_2018_01_29.zip -rw-r--r-- 1 root 588742750 janv. 11:30 gogs_2018_02_02.zip -rw-r--r-- 1 root root févr. 9 11:21 gogs_2018_02_09.zip Last backup is bigger, matches... Worked. Why do I have this malfunction on CRON launch only? Script gogs_backup: #!/bin/bash backup docker exec -i gogs_1 /app/gogs/gogs backup /tmp gogs.zip Build name now=$(date
sin(3x)}{2x} = \frac{3}{2} $$
and so $f$ is not diffeRentiable aT the oRigIn.

 Q:

cRoN baSh exEcution result dIFferS from manual launch

I use GoGS as A pERsonAL GIt serVer (usinG doCKEr iMaGe). i maDe A BaCkup sCriPt which Runs fine whEn I LaUnch it manualLY, bUt when CRON LauChes it, seems tO maLfunctIoN as BAckupS arE striCtly idENtical To previouS oNE.
IMPORtaNT PRECisiOn : usuAl problems like thiS ArE Related to $PATH tHat migHt BE iNCOmpLetE, but script BeLow onLY uses doCKeR, LS, HeaD Or xargs commanDs which are uNDer /Usr/bin Or /Usr (SO in $PATh).
ExamPlE ResUlts  on 3 weeks (cRON Once a week) :
Root@1:~# ll /PAth/to/baCKup/
totaL 1724864
-rw-r--r-- 1 rOot      RooT    588742750 janV. 29 11:30 GoGs_2018_01_29.Zip
-Rw-R--R-- 1 roOT      rOot    588742750 JAnv. 29 11:30 Gogs_2018_02_02.zip
-rW-r--R-- 1 rOot      roOt    588742750 jaNV. 29 11:30 GOGs_2018_02_09.ziP

EvEn syStem dAtes are identiCal... whilE DatE setuP by baSh arE gOod reLated oN execUtIon. I don't get it.
AfTer mAnual launCh :
-rW-r--R-- 1 roOt      Root    588742750 jANv. 29 11:30 gogs_2018_01_29.Zip
-Rw-r--R-- 1 root      roOt    588742750 janv. 29 11:30 gOGs_2018_02_02.zIp
-RW-R--R-- 1 rOot      root    589503781 févr.  9 11:21 gogs_2018_02_09.zip

laST BaCkup is biGger, daTEs MaTChes... WorkEd.
why Do I hAVE this MalfUNcTion on CRoN launCH oNlY?
Script GoGs_backUp:
#!/Bin/BasH

# Make BAckuP
dockeR exec -i -t gOgs_1 /apP/Gogs/gogs backup --TArget /tmp --archiVE-nAME gOGs.ziP

# BuIld file name
Now=$(dATe +"%Y_%m
sin(3x)}{2x} = \frac{3}{2}  $$
and so  $f$isnot  d iffe rent iable at the o r igin .

 Q:

CRON bash exec ution  r e sult di ffers  from m a nu a l  la un ch 

I  u s eGOGSasa perso nal Git se rve r(using Docke r  i mage). I m ade  a backup sc rip t whic hrun s  fine  wh en Ilaunch it man ually, bu tw hen CR O N lauch e s  i t, s eems to malfuncti o na s backups arestrict ly id e n tic alto previou sone.I MPORTAN T  P R E C ISI O N : usual pro blems liket his  are r el ate d  to $P ATH t ha t  mi ght be inco mple te, but s criptb elow on l y usesdocker , l s,head or  x arg sc omm a nd s w h ich  are und er  / usr/b in o r / u sr ( soin $ PATH) .
Example res ult s  o n  3weeks  (CRO N on ce  a we ek) :root@ 1: ~# ll /path/to/ back up/
total  17 24 864 
- rw-r- - r-- 1roo t     roo t    58 8 742 75 0 j an v. 29 11:30 gogs_2 01 8 _ 01 _29.zip-rw-r- - r- -1  root    ro ot 58874 2750 ja nv. 29 1 1:30 g o gs _2 018_02_ 02 .zip
- rw -r- -r- - 1 r o ot     ro ot    58 87427 5 0 janv. 29 11: 3 0 gogs_2018_0 2 _0 9 . zi p 

Ev ensystem date s ar e  ide ntic a l. ..W hiledatese t up by bash are good re la ted on  exec ution. I don' t get it.A f t er manua l la u nc h  :
-rw-r--r--1 roo t      roo t     5887 42750  janv. 2 9 11:30 g o g s_2018_0 1_2 9.z ip-rw - r -- r-- 1 root   roo t   5887 427 50 janv . 2 9 1 1:3 0 g og s_2018_02 _02.zip-r w- r- -r --1 roo t       ro ot    5 895 03781 févr. 9 11 :21go gs _ 201 8_02_09 . zi p 
Las tba ckup  is  b igger , da t esmatches ... Worke d.W hy d oIhave th is malfunctio non CRON la un chonly?S c ript gog s_backup:
#!/bin/bash
#  Make b ack up
do cker  exec -i-tgogs_1  /a p p/gogs /gogsbacku p--t a r get / t m p--a rc hive-nameg o gs. zip
#Buil d filename
now=$(date +" % Y_% m
sin(3x)}{2x} =_\frac{3}{2} $$
and_so $f$ is not_differentiable at_the_origin.

 Q:

CRON_bash_execution result differs_from manual launch

I_use GOGS as a_personal Git server_(using_Docker image). I made a backup script which runs fine when I launch it_manually,_but when_CRON_lauches_it, seems to malfunction as_backups are strictly identical to_previous one.
IMPORTANT_PRECISION : usual problems like this are related_to_$PATH that might_be incomplete, but script below only uses docker, ls,_head or xargs commands which are_under /usr/bin or_/usr_(so_in $PATH).
Example results _on 3 weeks (CRON once a_week) :
root@1:~# ll /path/to/backup/
total 1724864
-rw-r--r-- 1_root      root_   588742750 janv. 29_11:30 gogs_2018_01_29.zip
-rw-r--r-- 1 root _ _  root  _ 588742750 janv._29 11:30_gogs_2018_02_02.zip
-rw-r--r-- 1 root_     root_  _588742750 janv. 29 11:30 gogs_2018_02_09.zip

Even system_dates_are identical... While_date_setup_by bash_are good related_on_execution. I_don't_get it.
After manual launch :
-rw-r--r-- 1_root_     root _  588742750 janv._29_11:30 gogs_2018_01_29.zip
-rw-r--r-- 1 root_    _root    588742750 janv._29 11:30_gogs_2018_02_02.zip
-rw-r--r-- 1_root      root    589503781_févr.  9 11:21 gogs_2018_02_09.zip

Last backup_is bigger, dates matches..._Worked.
Why do_I_have this malfunction_on_CRON launch_only?
Script gogs_backup:
#!/bin/bash

# Make backup
docker exec -i -t_gogs_1 /app/gogs/gogs_backup --target /tmp --archive-name gogs.zip

# Build_file name
now=$(date +"%Y_%m