Excellent tip.... I was trying to accomplish this myself and such an
obvious technique never entered my mind.... Thanks!!!
Regards,
Hank Arnold
Florian Frommherz wrote:
You can't, as Group Policy logon/startup scripts will always execute on
startup. But you can have a workaround: execute the script and after its
initial completion, create a textfile or whatever to check for when
executed once more. By checking then for the file, you'll be able to
tell whether the script got executed before or not.
Re: Trouble starting MySQL [SOLVED?] ... it started mysql as can be seen above from ... Do not _execute_ anything from rc.conf for startups. ... Make your script take a 'start' as its first argument. ...startup script in /usr/local/etc/rc.d when you do the install. ... (freebsd-questions)
Re: Brightness issue with my laptop - Ubuntu 8.10 ... During every startup the brightness changes ... As stated the problem is that it has to be run as root.... I've noticed that the script has to be executed *after* ... It runs fine when I manually execute it as root only, ... (comp.unix.shell)
Re: Brightness issue with my laptop - Ubuntu 8.10 ... During every startup the brightness changes ... I've noticed that the script has to be executed *after* ... It runs fine when I manually execute it as root only, ... Make sure the script has at proper permissions,... (comp.unix.shell)
Re: run once logon script ...khmmc wrote: ..."Florian Frommherz" wrote: ... But you can have a workaround: execute the script and after its initial completion, create a textfile or whatever to check for when executed once more. ... (microsoft.public.win2000.group_policy)
Problems with IPFilter ... We are experiencing problems with IPNat at startup since it doesnt work. ... Once it is up and running the machine we execute the script in /etc/rc2.d: ... It seems like there is a kernel module not loaded in the moment of startup when the script is executed... ... (SunManagers)
