[01:27] <hellowar> hi
[01:27] <kernal> hi
[01:27] <hellowar> how its work this channel ? its used for ?
[01:28] <kernal> Topic for #ubuntu-mate is: Home of Ubuntu MATE | https://ubuntu-mate.org/ | Community https://ubuntu-mate.community/ | Donate https://ubuntu-mate.org/donate/ | IRC Logs http://irclogs.ubuntu.com/
[01:51] <mate|19370> hello, i'm looking for help. i'm not receiving email confirmation emails
[01:51] <kernal> hello
[01:51] <kernal> sounds like an email isssue
[01:51] <mate|19370> hi
[01:52] <kernal> not really a ubuntu mate issue
[01:52] <mate|19370> I've checke
[01:53] <mate|19370> i've checked my mailbox it worked; i can receive test emails..
[01:54] <kernal> alright, how is your email linked to a problem with ubuntu mate?
[01:55] <kernal> who is your email provider?
[01:57] <mate|19370> i'm trying to signup with the ubuntu-mate community (through the website).
[01:57] <mate|19370> What is the support email address for the ubuntu-mate community?
[01:59] <mate|19370> i have my own email-domain (with webhoster).
[02:00] <mate|19370> thanks for responding!
[02:00] <kernal> I'm just signing up now myself
[02:01] <kernal> and I just received an email
[02:01] <kernal> "Welcome to Ubuntu MATE Community!
[02:01] <kernal> Click the following link to confirm and activate your new account:"
[02:01] <kernal> it was very quick to receive the activation email
[02:05] <mate|19370> Thank you. i'll try again tomorrow. This link email has yet to arrive for me after several attempts.
[02:05] <mate|19370> bye.. bedtim
[03:29] <Boyette> hi
[03:29] <kernal> hi
[03:30] <Boyette> wow there are really ppl alive here
[03:30] <kernal> :P
[03:30] <Boyette> didnt even know this still existed
[03:30] <Boyette> this whole irc thing
[03:30] <Boyette> but its alive and kicking
[03:31] <kernal> still existed??? It never left
[03:31] <Boyette> apparently
[03:33] <Boyette> im stuck on some cron problem it must be very simple but i cant fix it
[03:33] <Boyette> i was hoping to find some living soul who can enlighten me
[03:34] <kernal> i don't normally tell dad jokes, but when i do he laughs
[03:34] <Boyette> that sounds like alive
[03:35] <kernal> shoot
[03:36] <kernal> although, I'm still rather new with ubuntu
[03:36] <Boyette> i have crontab setup to run 4 times a sh script a day
[03:36] <Boyette> script 1 compiles a file
[03:36] <Boyette> script 2 ftp's the file to another server
[03:36] <Boyette> script 3= scipt 1
[03:36] <Boyette> script 4 = script 2
[03:36] <Boyette> script 1 and 3 runs fine
[03:37] <Boyette> script 2 and 4 never run however crontab does compile a logfile which is always empty
[03:37] <Boyette> but is touched at the right time
[03:37] <Boyette> syslog reports:
[03:37] <kernal> using sftp to transfer the file?
[03:38] <Boyette> CRON [2340] (root) CMD (bash /root/ftp.sh  >> root/cronjobs1.log)
[03:38] <Boyette> CRON info NO MTA installed, discarding output)
[03:38] <Boyette> if i run the ftp.sh manually it runs fine
[03:39] <Boyette> but if cron has to do it automated it is just not doing anything
[03:39] <Boyette> but i cant find a clue why
[03:39] <kernal> have you used the full path names? that has caught me out before
[03:39] <Boyette> the pathnames must be correct
[03:40] <Boyette> ftp.sh is in the same directory
[03:40] <kernal> like /home/$USER/some/folder  |  not just some/folder
[03:40] <Boyette> as makethefuckingfile.sh
[03:40] <Techman> So, is anyone in here running the 18.04 dailies?
[03:40] <Boyette> and makethefuckingfile.sh does work
[03:40] <Boyette> thats me mr techman
[03:40] <Techman> I kinda wanna check out the progress with the dash menu and stuff with MATE
[03:40] <Boyette> im on mate 18,04
[03:40] <kernal> @Techman, no 18.04 for me yet
[03:40] <Techman> Not sure if it's stable enough to look on with a liveusb
[03:41] <Boyette> its very stable
[03:41] <Techman> I know wimpy was saying a few weeks ago that stuff was being moved around a lot
[03:41] <Boyette> only mesa is not
[03:41] <Boyette> but this problem i have btw is not on mate 18,04 but 16
[03:41] <Techman> Oh, don't mind me
[03:41] <Boyette> well matepanel gets fuckeed up sometimes
[03:41] <Techman> I just asked a question without watching what the previous conversation was
[03:41] <Boyette> yes
[03:41]  * Techman goes back to idling
[03:42] <Boyette> i was asking some help with my cron sh problem
[03:42] <Boyette> did u get me mr. kernal?
[03:43] <Boyette> if path was incorrect script2 would also not run
[03:45] <kernal> https://askubuntu.com/questions/23009/why-crontab-scripts-are-not-working
[03:46] <Boyette> permission problems
[03:46] <Boyette> i have looked into that
[03:46] <Boyette> chmod 755
[03:46] <Boyette> chmod +x
[03:46] <kernal> sorry bud, still a lot to learn myself
[03:47] <Boyette> hehe ok
[03:47] <Boyette> its actually a common problem
[03:47] <kernal> got a pastebin of the script?
[03:47] <Boyette> probably
[03:47] <Boyette> the ftp script?
[03:47] <kernal> yeah
[03:48] <Boyette> just a moment
[03:48] <Boyette> need to copy from the server
[03:50] <Boyette> #!/bin/sh
[03:50] <Boyette> HOST='ftp.server.com'
[03:50] <Boyette> PORT='21'
[03:50] <Boyette> USER='email@domain.com
[03:50] <Boyette> PASSWORD='xxxxxxxxxx'
[03:50] <Boyette> FILE='xxx.xml'
[03:50] <Boyette> ftp -n $HOST $PORT <<END_SCRIPT
[03:50] <Boyette> quote USER $USER
[03:50] <Boyette> quote PASS $PASSWORD
[03:50] <Boyette> put $FILE
[03:50] <Boyette> quit
[03:50] <Boyette> END_SCRIPT
[03:50] <Boyette> exit 0
[03:50] <Boyette> but that runs well if i run it manually
[03:51] <kernal> try changing the file path
[03:51] <kernal> that's what I meant about full paths
[03:51] <Boyette> the file path in cron ?
[03:51] <kernal> in the script
[03:51] <kernal> FILE='xxx.xml'
[03:51] <Boyette> the file is in the same directory as the ftp.sh
[03:51] <kernal> put in the full path
[03:52] <kernal> I know, but in cron it likes to have the full path
[03:52] <kernal> ????
[03:52] <Boyette> i think its not the file because cron would log that and it doesnt make sense that the script itself runs fine but not if cron does that
[03:52] <Boyette> in cron the full path to the ftp.sh is there
[03:52] <kernal> this has caught me out before with some shell scripts that run on cronjobs
[03:52] <Boyette> it doesnt need to know a path to a file in the script because cron is starting the script not executing the actual ftp transaction
[03:53] <Boyette> i can however do it
[03:53] <Boyette> it would also not hurt
[03:53] <kernal> can't hurt to test
[03:53] <Boyette> agree
[03:54] <kernal> https://unix.stackexchange.com/questions/38951/what-is-the-working-directory-when-cron-executes-a-job
[03:55] <Boyette> ok
[03:55] <Boyette> that is actually referring to a similar problem
[03:55] <Boyette> if cron would give that error
[03:55] <Boyette> but it doesnt give the error
[03:55] <Boyette> it seems it can just not run the script at all
[03:55] <Boyette> it seems its already getting terminated before it even executed the script
[03:56] <Boyette> but it also doesnt give an error about not being able to execute it
[03:56] <Boyette> only syslog gives error about creating the output for that.. which i also dont understand
[03:56] <Boyette> but i adjusted it now
[04:00] <Boyette> now the script doesnt like this
[04:04] <kernal> ??
[04:05] <kernal> what's does the entry in cron look like?
[04:06] <Boyette> ftp needs a specific file.. its not used to read paths
[04:06] <Boyette> thats unusual
[04:06] <kernal> add a 'cd' into to your script then, to get cron to change into that directory
[04:07] <Boyette> 0 4 * * 0-6 bash /root/x/run.sh >> /root/wg/cronjobs1.log
[04:07] <Boyette> 0 10 * * 0-6 bash /root/xftp.sh >> /root/wg/cronjobs2.log
[04:07] <Boyette> 0 13 * * 0-6 bash /root/x/run.sh >> /root/wg/cronjobs3.log
[04:07] <Boyette> 0 22 * * 0-6 bash /root/x/ftp.sh >> /root/wg/cronjobs4.log
[04:08] <Boyette> 0 4 * * 0-6 bash /root/x/run.sh >> /root/wg/cronjobs1.log
[04:08] <Boyette> 0 10 * * 0-6 bash /root/x/ftp.sh >> /root/wg/cronjobs2.log
[04:08] <Boyette> 0 13 * * 0-6 bash /root/x/run.sh >> /root/wg/cronjobs3.log
[04:08] <Boyette> 0 22 * * 0-6 bash /root/x/ftp.sh >> /root/wg/cronjobs4.log
[04:08] <Boyette> run.sh is executed fine
[04:08] <Boyette> ftp.sh is just not running
[04:09] <Boyette> cronjobs2.log and cronjobs4.log are created or touched at the correct times but always stay completely empty
[04:09] <Boyette> while log 1 and 3 are written
[04:09] <kernal> add a 'cd /root/x/' to the start of the script, so when it's run from cron it's working in the right directory
[04:10] <Boyette> but it is already in the right directory
[04:10] <Boyette> if that would be the issue why would run.sh work well
[04:10] <Boyette> it has to do a lot of things
[04:10] <kernal> assuming that's where the '.xml' file is located that you want to ftp
[04:10] <Boyette> in that same directory
[04:10] <Boyette> yes the xml is located there
[04:10] <Boyette> run.sh is located there
[04:10] <Boyette> ftp.sh is located there
[04:10] <Boyette> and run.sh creates the xml
[04:11] <Boyette> that all works fine
[04:11] <kernal> when cron runs it's just calling the script from that directory, it's not working in that directory
[04:11] <kernal> so when it looks for 'xxxx.xml' it can't find it
[04:11] <Boyette> ok but the script itself only has to startup thats crons task
[04:12] <Boyette> not running the script right?
[04:23] <Boyette> i added cd /*/* in the beginning
[04:24] <kernal> what does cd '/*/*' do?
[04:25] <kernal> bash: not a directory
[04:26] <Boyette> cd /root/x/
[04:29] <Boyette> well see how this goes
[04:35] <kernal> good to learn, just wrote a small script myself and set it to run on crontab
[04:35] <kernal> it detects if a file exists and it it does it will 'cat' it
[04:35] <kernal> if not it will echo "File does not exist"
[04:36] <kernal> the cronjob just ran
[04:36] <kernal> and in the log 'File does not exist'
[04:37] <kernal> but if I run the script myself and I'm in that directory...
[04:37] <kernal> Found file.
[04:37] <kernal> Hello World!
[04:37] <hggdh> kernal: when you run cron, yo have to set your environment. Cron cleans up the user's environment before allowing a script to run
[04:37] <Boyette> ok
[04:38] <kernal> #!/bin/sh
[04:38] <kernal> file="xxx.xml"
[04:38] <kernal> if [ ! -f $file ]; then
[04:38] <kernal>   echo "File not found."
[04:38] <kernal> else
[04:38] <kernal>   echo "Found file."
[04:38] <kernal>   cat $file
[04:38] <kernal> fi
[04:38] <hggdh> kernal: usepastebin
[04:38] <hggdh> use pastenbin
[04:39] <kernal> aye
[04:39] <hggdh> and, yes, this script will most certainly not quite work the way you  want under cron
[04:39] <kernal> I know mate, just showing Boyette as a test
[04:39] <Boyette> ok
[04:40] <Boyette> so how exactly will it work?
[04:40] <Boyette> #!/bin/sh
[04:40] <Boyette> cd /root/x/
[04:40] <Boyette> HOST='ftp.server.com'
[04:40] <Boyette> PORT='21'
[04:40] <Boyette> USER='xxxxxx'
[04:40] <Boyette> PASSWORD='xxxxxx'
[04:40] <Boyette> FILE='xxxxx.xml'
[04:40] <Boyette> ftp -n $HOST $PORT <<END_SCRIPT
[04:40] <Boyette> quote USER $USER
[04:40] <Boyette> quote PASS $PASSWORD
[04:40] <hggdh> ...
[04:40] <Boyette> put $FILE
[04:40] <Boyette> quit
[04:40] <Boyette> END_SCRIPT
[04:40] <Boyette> exit 0
[04:40] <hggdh> Boyette: UESE PASTEBIN
[04:40] <Boyette> like this?
[04:41] <Boyette> https://pastebin.com/rLF785iT
[04:41]  * kernal steps out for luch
[04:42] <hggdh> Boyette: if your FTP server accepts the syntax you used for commands, it should work
[04:42] <Boyette> the ftp server accepts it
[04:42] <Boyette> if i run the script manually it runs fine
[04:43] <Boyette> but the problem is that cron doesnt do it
[04:44] <Boyette> cron
[04:44] <Boyette> https://pastebin.com/DxcWcSWK
[04:44] <Boyette> 1 and 3 runs fine
[04:44] <Boyette> 2 and 4 doesnt run
[04:44] <Boyette> creates empty log file but the log is touched at the correct times
[04:46] <hggdh> Boyette: on the shebang, add '-x' so it will read #!/bin/sh -x
[04:47] <hggdh> then run it under cron again
[04:48] <Boyette> add -x
[04:48] <Boyette> what is that doing
[04:48] <hggdh> it will give you a "trace" of the commands executed by the shell
[04:49] <Boyette> aah
[04:49] <Boyette> yes that was missing aswell
[04:49] <Boyette> i had a different script before using bash instead of sh
[04:49] <Boyette> there i got a trace
[04:50] <Boyette> but i thought cron had trouble with bash so i changed it to sh then i lost the trace
[04:50] <hggdh> you might also need a line after the shebang with "exec 2>&1"
[04:50] <hggdh> cron has no problems with bash, sh, or any other shell
[04:50] <Boyette> well im stuck on this really not understanding why cron doesnt run this
[04:51] <Boyette> because empty logfile
[04:51] <hggdh> actually, change the exec to exec 2>&1 > /tmp/$0.log
[04:51] <Boyette> ok
[04:51] <Boyette> only in syslog i see this
[04:51] <Boyette> CRON [2340] (root) CMD (bash /root/ftp.sh  >> root/cronjobs1.log)
[04:51] <Boyette> CRON info NO MTA installed, discarding output)
[04:52] <hggdh> this is just telling you cron will not email you the output because you do not have a MTA installed
[04:53] <Boyette> yes
[04:53] <hggdh> change  the 'exec' lne as I pointed out
[04:53] <Boyette> i know but what i dont understand is why its also not logging it as its told to do
[04:53] <Boyette> like this?
[04:53] <Boyette> https://pastebin.com/QRMdkssX
[04:54] <hggdh> the exec is on its own line, after the shebang
[04:54] <hggdh> exec 2>&1 > /tmp/$0.log
[04:55] <hggdh> wait
[04:56] <hggdh> change the $0 to a string, you are running it with a full path
[04:56] <Boyette> ok
[04:56] <hggdh> line: exec 2>&1 > /tmp/cron-out.log
[04:56] <hggdh> brb
[04:57] <Boyette> https://pastebin.com/hB2MDRem
[05:02] <hggdh> yes
[05:02] <Boyette> correct?
[05:03] <hggdh> after running it thru cron look at /tmp/cron-out.log
[05:04] <Boyette> ok
[05:04] <Boyette> i will
[05:04] <Boyette> hopefully this works now
[05:04] <Boyette> my final goal is actually another step ahead
[05:04] <hggdh> it will not, but it will show you what happened
[05:05] <Boyette> hehe  ok
[05:05] <Boyette> first i want those 2 scripts to run after the other one is finished
[05:05] <Boyette> but the ftp.sh i couldnt make it happen automatically
[05:05] <Boyette> if this finally works
[05:05] <Boyette> what would actually be more nice if it can always keeps running
[05:06] <Boyette> so when 1 stops the other one starts and when that is finished the other one starts
[05:06] <Boyette> do u understand what I mean?
[05:06] <Boyette> like a neverending process
[05:07] <hggdh> well... this is not exactly what you showed us in the crontab. There the scripts are set to run at specific times
[05:07] <Boyette> yes i know
[05:07] <Boyette> because i dont know how to do that like the way i was saying
[05:07] <Boyette> so i was thinking of first running it like this 2 times a day
[05:08] <Boyette> but better would be that the other sh is always starting when the other stops
[05:08] <Boyette> but i dont know if crontab supports that at all
[05:08] <Boyette> because it looks pretty time based to me
[05:09] <hggdh> cron actions are time-based, on the schedule you provided
[05:09] <Boyette> yes so what i want cant be achieved with crontab at all?
 perhaps. if you want script2 to be run after script1, then probably the easiest way is to merge both of them
[05:11] <Boyette> thats impossible
[05:11] <Boyette> i think
[05:11] <Boyette> :P
[05:11] <Boyette> but would actually make sense
[05:13] <Boyette> but the problem is i think that in the run.sh is not defined when the script stops
[05:13] <Boyette> it just stops when its finished
[05:14] <Boyette> so how to determine that
[05:14] <hggdh> it ends at the end of the script
[05:14] <Boyette> this is the run.sh
[05:14] <Boyette> https://pastebin.com/yAENyPCq
[05:14] <kernal> put the commands from script2 into the bottom of script1
[05:14] <kernal> making only one script
[05:15] <Boyette> this is script 1
[05:15] <Boyette> e script
[05:15] <kernal> that way the fpt will only start after the commands from script1 has finished
[05:15] <Boyette> https://pastebin.com/yAENyPCq
[05:15] <Boyette> can it really be added there?
[05:15] <Boyette> because it using mono
[05:15] <Boyette> and .exe
[05:16] <hggdh> yes. Now, if the call to mono will ever end, this is a different issue
[05:16] <Boyette> exactly
[05:16] <Boyette> that will just end when its finished doing its business
[05:16] <Boyette> but the script is just to start that not to end that process
[05:17] <Boyette> thats why i was doing it like this with enough time to be sure its finished
[05:17] <hggdh> no...
[05:18] <kernal> bash will only move onto the next line/command if the previous line/command has finished
[05:18] <Boyette> so if the process is still running it will know?
[05:18] <hggdh> let's suppose, for the sake of argument, the the program called by mono DOES end. It may take a few seconds, or a few hours
[05:18] <hggdh> I do not really care
[05:18] <Boyette> yes it takes hours
[05:19] <hggdh> AFTER the mono program ends, then the next script line will be executed (exit 0)
[05:19] <hggdh> so, add your second script before the exit 0 line
[05:19] <Boyette> quit 0 you mean ?
[05:20] <hggdh> yes
[05:20] <hggdh> and I am pretty sure this script is being re-purposed
[05:21] <Boyette> so like this ?
[05:21] <Boyette> https://pastebin.com/vZKV1z6V
[05:23] <hggdh> almost. move the 'exec 2>&1 ...' to the top, after the real shebang
[05:25] <Boyette> like this
[05:25] <Boyette> https://pastebin.com/4pPB29sq
[05:25] <Boyette> but actually this script does log very well
[05:25] <Boyette> in crontab1 and 3
[05:25] <Boyette> already
[05:28] <hggdh> as you wish, then
[05:28] <Boyette> but it doesnt matter
[05:28] <Boyette> to make 2 logs
[05:28] <Boyette> do you think its fine like this?
[05:28] <Boyette> https://pastebin.com/4pPB29sq
[05:28] <hggdh> yes
[05:29] <Boyette> ok but if this works
[05:29] <Boyette> its just 1 process now
[05:29] <hggdh> yes
[05:29] <Boyette> but how do we make sure that 1 process is restarting as soon as its finished?
[05:29] <Boyette> or always running
[05:30] <hggdh> then you have to change the logic
[05:30] <hggdh> but this is not something I have time to do now
[05:30] <hggdh> (heading for bed)
[05:30] <Boyette> ok
[05:30] <Boyette> do u have 1 minute
[05:30] <hggdh> 1 minute
[05:30] <Boyette> i will check what happens if i do run.sh now
[05:30] <hggdh> via cron
[05:31] <Boyette> manually
[05:31] <Boyette> it should also work
[05:31] <hggdh> but your probme is with cron
[05:31] <hggdh> ah well
[05:32] <Boyette> well
[05:32] <Boyette> not anymore if the 2 scripts are 1 now
[05:32] <Boyette> because 1 runs fine
[05:32] <Boyette> it wont suddenly stop doing that i suppose
[05:33] <hggdh> Boyette: you really do not know shell scripting, do you?
[05:34] <Boyette> i dont
[05:34] <Boyette> i used google
[05:34] <kernal> your original problem was that the ftp did not run in cron?
[05:34] <Boyette> for all of this so far
[05:34] <hggdh> ah
[05:34] <Boyette> yes
[05:34] <kernal> and you said it would run when you manually run it
[05:34] <Boyette> yes it did
[05:34] <kernal> so manually running it now, it will prob work again
[05:35] <hggdh> you need to start learning :-)
[05:35] <Boyette> well but now we merged it
[05:35] <kernal> circling back to your original problem, that it won't run in cron again
[05:35] <hggdh> yes, it should work (if It was before, manually) with the two script together
[05:35] <Boyette> but it doesnt run anymore  :P
[05:35] <Boyette> manually
[05:35] <hggdh> but it will most probably fail the same under cron
[05:36] <hggdh> OK. pastebin the log
[05:36] <Boyette> just saying
[05:37] <Boyette> line2: /tmp/cron-out.log: no such file or directory
[05:37] <Boyette> i have to make it in root i think
[05:37] <hggdh> you do not have /tmp?
[05:38] <hggdh> dammit
[05:38] <Boyette> apparently
[05:38] <hggdh> exec 2>&1 > /tmp/cron-out.log
[05:38] <Boyette> no
[05:38] <hggdh> we missed the second '>'
[05:38] <Boyette> i do have a tmp
[05:39] <Boyette> ah ok
[05:40] <Boyette> now its running
[05:40] <Boyette> but i dont see anything in terminal anymore
[05:40] <Boyette> so i cant see what its doing
[05:40] <Boyette> just blinking cursor
[05:40] <Boyette> probably because it writing only to the log now
[05:40] <hggdh> no, you will not, since it is writing to /tmp/cron-out.log
[05:40] <Boyette> actually more tidy
[05:41] <hggdh> BEFORE pastebinning the log -- sanitise the output (server address, user, password)
[05:41] <Boyette> yes its working
[05:41] <Boyette> i can see in the cron out log now that its doing its job
[05:41] <hggdh> yes, it would work (based on you asserting it was working manually before)
[05:42] <hggdh> it is the cron run that will fail
[05:42] <Boyette> well this script 1 was also working with cron
[05:42] <Boyette> but script 2 not
[05:42] <Boyette> but according to the fact that script 2 is now in script 1 it will be fine with only script 1
[05:42] <hggdh> and, since script 1 is now followed by script 2, then it will fail
[05:42] <Boyette> unless cron is now also struggling on script 1 because it doesnt like script 2 in there
[05:42] <Boyette> maybe
[05:42] <Boyette> well see
[05:42] <hggdh> nothing to do
[05:43] <Boyette> but we adjusted that aswell
[05:43] <hggdh> script 2 (embedded in the first script will fail because it was failing before
[05:43] <hggdh> and nothing was changed
[05:43] <Boyette> but the script itself was not failing .. only when cron runned it
[05:43] <Boyette> so probably this time it will work because i runned it manually
[05:43] <hggdh> yes. I know. And this is what I have been telling you
[05:44] <Boyette> but when cron runs it next time we will see
[05:44] <Boyette> yes exactly
[05:44] <Boyette> but we also added the call to the directory
[05:44] <Boyette> which might solve it
[05:44] <hggdh> you will find out
[05:44] <hggdh> :-)
[05:44] <hggdh> and... I am out
[05:44] <Boyette> thank you sir!
[05:44] <hggdh> yw
[05:45] <Boyette> kernal are you still there?
[05:45] <kernal> no
[05:45] <Boyette> lol
[05:45] <Boyette> i think u were completely right in the first place
[05:45] <Boyette> look at this
[05:45] <Boyette> CRON [2340] (root) CMD (bash /root/ftp.sh  >> root/cronjobs1.log)
[05:45] <Boyette> that was in the original systemlog
[05:45] <Boyette> /root/ftp.sh   (this is incorrect)
[05:45] <Boyette> should be
[05:46] <Boyette> /root/x/ftp.sh
[05:46] <Boyette> which is indicating that crontab tries to run ftp.sh from root
[05:46] <Boyette> where it is not located
[05:46] <Boyette> thats exactly what u pointed out
[05:46] <kernal> ;)
[05:46] <Boyette> i just noticed when i send that line again to hggdh
[05:46] <kernal> bloody pull paths and cron
[05:47] <Boyette> it never catched my eye
[05:47] <Boyette> so probably the cd command is already solving it all
[05:48] <Boyette> and my mistake was it didnt matter because run.sh worked fine.. but run.sh is not pointing out to any local directory.. it goes online
[05:48] <Boyette> so the problem was not applicable to run.sh because it doesnt use any local directions
[05:48] <Boyette> thats my mistake where i went thinking in the wrong direction
[05:48] <kernal> hggdh, seems very knowledgeable
[05:49] <Boyette> i think he is a programmer
[05:49] <Boyette> but to be honest this is actually not rocket science
[05:49] <Boyette> but he knows shell scripting
[05:49] <Boyette> i dont
[05:49] <Boyette> i just googled it all so far
[05:51] <Boyette> anyway thank you very much
[05:51] <Boyette> lets hope this fixed it
[05:51] <Boyette> otherwise i really know now where the problem is
[05:53] <Boyette> and maybe this will make sure it always runs later
[05:53] <Boyette> https://stackoverflow.com/questions/298760/how-to-make-sure-an-application-keeps-running-on-linux
[05:57] <Boyette> out
[06:28] <Talikkaf> Is it possible to download a pre-release of Ubuntu MATE 18.04 (alpha, beta, RC or something similar?)
[06:29] <alkisg> Talikkaf: sure, there are the daily build isos available
[06:30] <Talikkaf> indeed
[06:30] <Talikkaf> silly me, why did I not google it.  http://cdimage.ubuntu.com/ubuntu-mate/daily-live/
[09:18] <mate|1240> i am having a problem with insync not starting in 17.10 can anybody help me ?
[12:51] <guest-xxfbec> hello
[12:52] <guest-xxfbec> anyone there
[12:52] <guest-xxfbec> pö
[12:52] <diogenes_> guest-xxfbec, 84 people total
[21:18] <Boyette> hi