DSM-G600, DNS-3xx and NSA-220 Hack Forum

Sorry for the late reply, but is it GPLed or something? Is it yours? Does it have a license?

I am really glad the source files are included, so may I eventually use it for a 100% Free Software DNS-323 firmware?

I think the possibility to call some user shutdown script would be useful. People might want to add calls to "smb stop" or "/ffp/etc/rc stop" before everything's killed.

Thank you very much for you reply Joao.

# Author: Joao Cardoso
# This file is in the public domain
# This software is provided as is, use as you fit, no warranty.

If you agree, I can add these three comment lines to the source files and then I will see if the sources can be covered under the GPL.

> I think the possibility to call some user shutdown script would be useful. People might want to add calls to "smb stop" or "/ffp/etc/rc stop" before everything's killed.

I agree, and I wiil implement it soon: read  the first non-blank/comment line from /ffp/etc/chkbutton2.conf and execute it, setting an alarm just in case the executed command never returns (5 secs?), ignoring its termination status, and then killing any leftover process and doing the reboot/shutdown.

> If you agree, I can add these three comment lines to the source files and then I will see if the sources can be covered under the GPL.

Sure, but it is, as it doesn't impose any limitations.
I will add those lines for version 0.2

>What a great script! I absolutely love it.
Quick question for the quasi-illiterate: is it recommended that one uninstall cleanboot if chkbutton2 is installed? Does chkbutton2 update the 'halt' and 'shutdown' commands for example that cleanboot does?

It's not a script, but a compiled program ;-)
It does not interact with cleanboot, but cleanboot's shutdown will not work, as it relies on the original chkbutton, which watch the existence of a file named /tmp/shutdown.

This makes me wonder if chkbutton2 should'nt also look for the presence of that file... yes, maybe...

jcard wrote:

> I think the possibility to call some user shutdown script would be useful. People might want to add calls to "smb stop" or "/ffp/etc/rc stop" before everything's killed.

I agree, and I wiil implement it soon:

Thanks for the great little tool. Since installing it I have noticed the light behind the power button no long dim's to indicate the unit is asleep. Does this mean the unit isn't going to sleep?

I'm looking forward to the those shutdown scripts!

krimb1 wrote:

rcblackwell wrote:

Since installing it I have noticed the light behind the power button no long dim's to indicate the unit is asleep. Does this mean the unit isn't going to sleep?

I think the unit is going to sleep, but is not showing it. I can see the drives go to sleep via 'logread' but of course would like to see it via the LED as well!

Many thanks to your great work.

The program doesn't depend on anything which is on disk; ir runs from memory, is compiled against the unity firmware libraries and invoke the firmware busybox for a reboot.

As for the leds, in my CH3SNAS the power led doesn't dim when the disks spindow, and I can't manage that led... it's a firmware difference between dlink and conceptronic.

To know if the disks are or not spindown I just put my hand on the unity and feel or don't feel the motor disks  working... high tech last resort :-O

I have contradictory feelings about disk spindown -- energy saving for one side versus disk life for another.
I used to keep all my PCs always on, 24/7, and only once I got a disk failure; my disks last for 5 or 6 years! and I only replaced them because they become "small".

The problem is the number of start/stop and head retract cycles, which are limited for a given disk -- most of the time disks fail because of mechanical failure related with those problems.
Thus, the problem is: what is cheaper (for my pocket and the planet): save a few cents of electricity / planet resources during two or three years, or have to buy/exaust planet resources every two or three years when buying a new disk?
I'm sure that someone has that bill done, but I don't know the results

I installed it but unfortunately had to disable it since after have this running, I can not access the standard DNS Web GUI. I have ffp running from USB drive. my Web GUI run at port 81 since the port 80 is used for lighttpd web hosting.

jcard wrote:

iazmin wrote:

I installed it but unfortunately had to disable it since after have this running, I can not access the standard DNS Web GUI. I have ffp running from USB drive. my Web GUI run at port 81 since the port 80 is used for lighttpd web hosting.

There is nothing in chkbutton2 thats makes other services stop working.

However, the init script /ffp/start/chkbutton2.sh stops the standard chkbutton, as it makes no sense to have both working.

In the standard firmware, there is a chain of processes launching other processes, and some processes check to see if other are running and re-launch them if they aren't. Perhaps the standard chkbutton launchs or re-launchs the web process?

As I have a Conceptronics CH3SNAS (which has the DNS323-revB hardware), I dont kown what processes launch other processes in DLINK's DNS323.

If you have some linux knowledge, perhaps you could try to diagnose the problem? For example, starting "chkbutton2" directly from the command line, instead of starting if from "/ffp/start/chkbutton2 start", and checking that you still have web services? then, terminating the standard chkbutton with the command "kill $(pidof chkbutton)" and see if you still have web?

What firmware version do you have?

i am using FW 1.06. I will try to troubleshoot tonight. your proposed troubleshooting make sense to know the error.

Here is version 0.2:

*  - The box back button is also monitorized for momentary pressing.
*  - Added one or two optional command line arguments, that must be the
*    absolute path name of executable scripts, owned by root and not
*    writable by anybody else.
*    The first script is executed before any other action is taken by this
*    program, and can do any cleanup needed before rebooting or shutdown.
*    The script must be completed in 5 seconds.
*    The second optional argument is the name of a script to execute when
*    the back button is momentary pressed and both front leds start flashing;
*    it can be used to start a backup, mount or umount an external USB disk...
*    This program does not wait for the termination of such script.
*
*    If you only need the second argument, just write the name of a
*    non-existing file as the first argument

By default, /ffp/start/chkbutton2.sh uses the do-nothing (but with instructions) scripts cleanup.sh and backup.sh found at /ffp/share/chkbutton2, but that can obviously be changed.

At least on my CH3SNAS there is no problem using the back reset button, as it needs to be pressed only momentary, and for a real reset it must be pressed for at least ten seconds (during bootup, I believe). But your firmware can be different -- backup your configuration first.

If it is not working for you, start first syslogd, "sh /ffp/start/syslogd.sh start" and watch the messages logged at /var/log/messages.

Enjoy,

---

Attachments:
chkbutton2-0.2.tgz, Size: 8,592 bytes, Downloads: 503

iazmin wrote:

I discovered that the chkbutton2 will work with Web GUI working, if I launch the chkbutton2 manually (outside of /ffp/start by running it from command line). Initially I tried to run it by placing the sh /anywhere/chkbutton2.sh start in fun.plug.local but the problem still persist.

I'm running into a similar problem. If chkbutton2 is launched during boot, at the appropriate spindown time, the fans and disks whir up to full speed and the DNS-323 will never sleep. It works just fine if I ssh into the box and launch chkbutton2 manually.

At first I started the script via the normal chmod a+x'ing it at run time in the /ffp/start folder, but when that didn't work I tried adding it to the fun_plug.local to see if that would do the trick. Didn't work at all.

Are others experiencing this as well? I hope I don't have to login each time to start this great script. I'm running on the 1.08 beta firmware at the moment.

I'm running into a similar problem. If chkbutton2 is launched during boot, at the appropriate spindown time, the fans and disks whir up to full speed and the DNS-323 will never sleep.

You mean that everything (chkbutton2 included ! ) works OK until spindown time?
And when the fan starts at full speed, does chkbutton2 still works?

When launched through ffp/start/, can you login, do a "ps" and see if the original chkbutton is running simultaneously with chkbutton2? It shouldn't.

It works just fine if I ssh into the box and launch chkbutton2 manually.

At first I started the script via the normal chmod a+x'ing it at run time in the /ffp/start folder, but when that didn't work I tried adding it to the fun_plug.local to see if that would do the trick. Didn't work at all.

This seems to indicate a problem with the order of the script execution... or permission problems.
To manually start the script do you login as root or as another user?
Have you changed the owner/permissions of the executable?

[edited] When you start it manually, do you do it using "/ffp/start/chkbutton2.sh start" or do you invoke it directly?

I have no clues...

Does chkbutton2 works for anybody  with FW-1.08? Positive answers are wellcome.

Last edited by jcard (2009-06-23 03:18:12)

I just realized something. When I upgraded to FW 1.08 beta, I reformatted my drives with ext3. Could that be the problem by any chance?